Triple
T21677150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Act of 1796 |
E534999
|
entity |
| Predicate | usesSurveySystem |
P12086
|
FINISHED |
| Object | rectangular survey system |
—
|
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: rectangular survey system | Statement: [Land Act of 1796, usesSurveySystem, rectangular survey system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSurveySystem Context triple: [Land Act of 1796, usesSurveySystem, rectangular survey system]
-
A.
usesSurveyOf
Indicates that one entity bases its work, analysis, or decision on data or findings obtained from a particular survey conducted by another entity.
-
B.
usesSurveyPoint
Indicates that an entity relies on or references a specific survey point as a positional or measurement basis in its activity or relationship.
-
C.
surveySystemType
chosen
Indicates the type or category of system used to conduct or manage a survey.
-
D.
hasSurveyRole
Indicates that an entity holds a specific role or responsibility within the context of a survey.
-
E.
coSurveyedWith
Indicates that two or more entities participated together in the same survey activity or data-collection effort.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a105b888190820b894d16c1ab77 |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:42 p.m.