Triple
T36320523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armstrong County, Texas |
E894318
|
entity |
| Predicate | hasHistoricRanch |
P25661
|
FINISHED |
| Object | JA Ranch (part) |
—
|
NE NERFINISHED |
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: JA Ranch (part) | Statement: [Armstrong County, Texas, hasHistoricRanch, JA Ranch (part)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricRanch Context triple: [Armstrong County, Texas, hasHistoricRanch, JA Ranch (part)]
-
A.
hasHistoricFarm
Indicates that an entity possesses, includes, or is associated with a farm that has historical significance or heritage value.
-
B.
hasRanch
chosen
Indicates that one entity owns, operates, or is associated with a ranch.
-
C.
hasHistoricLandGrants
Indicates that an entity has been granted land through one or more historically significant official land grants.
-
D.
hasFarmSystemHistoryWith
Indicates a historical relationship in which one entity has previously been part of, managed by, or otherwise involved with another entity’s farm system.
-
E.
hasFeralCattleSince
Indicates that feral cattle have been present in or associated with an entity continuously since a specified point in time.
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4:09 p.m.