Triple
T14053877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma land runs |
E338161
|
entity |
| Predicate | typicalHomesteadSize |
P19614
|
FINISHED |
| Object | 160 acres |
—
|
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: 160 acres | Statement: [Oklahoma land runs, typicalHomesteadSize, 160 acres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHomesteadSize Context triple: [Oklahoma land runs, typicalHomesteadSize, 160 acres]
-
A.
typicalHomeCapacity
Indicates the usual or standard number of occupants that a home is designed or expected to accommodate.
-
B.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
C.
estimatedFarmCount
Indicates the estimated number of farms associated with or present in a given context or entity.
-
D.
hasNumberOfAcres
chosen
Indicates the specific quantity of land area, measured in acres, that is associated with an entity.
-
E.
tenantFarmersCount
Indicates the number of tenant farmers associated with a particular landholding, property, or area.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8bc54c8190a12f0fc056568538 |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.