Triple
T9486843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | limitanei |
E228782
|
entity |
| Predicate | landGrants |
P62251
|
FINISHED |
| Object | often settled on military lands |
—
|
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: often settled on military lands | Statement: [limitanei, landGrants, often settled on military lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landGrants Context triple: [limitanei, landGrants, often settled on military lands]
-
A.
landGrantField
Indicates that a specific field or parcel of land has been allocated or granted, typically by an authority, to a recipient under a land grant arrangement.
-
B.
hasHistoricLandGrants
chosen
Indicates that an entity has been granted land through one or more historically significant official land grants.
-
C.
originalLandGrantBy
Indicates that an entity was granted land by a specified grantor in the original land grant transaction.
-
D.
landGrantDesignation
Indicates that an institution has been formally designated as a land-grant institution under a land-grant program or legislation.
-
E.
landGrantLocation
Indicates the geographic place or area to which a particular land grant applies or in which it is situated.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd8051303881909566126a2688e41c |
completed | April 1, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.