Triple
T14053876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma land runs |
E338161
|
entity |
| Predicate | methodOf |
P859
|
FINISHED |
| Object | allocation of homestead claims |
—
|
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: allocation of homestead claims | Statement: [Oklahoma land runs, methodOf, allocation of homestead claims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOf Context triple: [Oklahoma land runs, methodOf, allocation of homestead claims]
-
A.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
B.
usesMethods
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
C.
methodOfRule
Indicates the specific method, procedure, or approach by which a rule is applied, implemented, or enforced.
-
D.
adoptedByMethod
Indicates that something is accepted, implemented, or brought into use through a specified method or procedure.
-
E.
plannedMethod
Indicates that a particular method or procedure has been selected or designated in advance as the intended way to carry out an action or achieve a goal.
- 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.