Triple
T30681044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCO |
E781051
|
entity |
| Predicate | mayBeUsedInterchangeablyWith |
P5887
|
FINISHED |
| Object | Texas peace officer |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Texas peace officer | Statement: [TCO, mayBeUsedInterchangeablyWith, Texas peace officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeUsedInterchangeablyWith Context triple: [TCO, mayBeUsedInterchangeablyWith, Texas peace officer]
-
A.
isAlternativeTo
chosen
Indicates that one entity can serve as a substitute or different option in place of another.
-
B.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
C.
alternativeUsedBy
Indicates that one entity serves as an alternative option or substitute that is used in place of another entity.
-
D.
mayBeIntegratedWith
Indicates that one entity has the potential or capability to be combined or incorporated with another entity into a unified or interoperable whole.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 8:32 p.m.