Triple
T2340240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Ordinance of 1785 |
E45008
|
entity |
| Predicate | establishedUnit |
P28425
|
FINISHED |
| Object | township |
—
|
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: township | Statement: [Land Ordinance of 1785, establishedUnit, township]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedUnit Context triple: [Land Ordinance of 1785, establishedUnit, township]
-
A.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
B.
associatedUnitType
chosen
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
C.
eligibilityUnit
Indicates that one entity serves as the unit or basis used to determine another entity’s eligibility for a benefit, status, or condition.
-
D.
supportedUnit
Indicates that one entity provides assistance, resources, or backing to another entity functioning as a unit or sub-organization.
-
E.
establishedFollowing
Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.