Triple
T26958178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland state line |
E678964
|
entity |
| Predicate | partlySurveyedBy |
P163077
|
FINISHED |
| Object | Charles Mason |
—
|
NE NERFINISHED |
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: Charles Mason | Statement: [Maryland state line, partlySurveyedBy, Charles Mason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlySurveyedBy Context triple: [Maryland state line, partlySurveyedBy, Charles Mason]
-
A.
surveyedIn
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
B.
surveyedFor
Indicates that one entity has been examined, questioned, or assessed in order to gather information specifically about another entity or topic.
-
C.
usesSurveyOf
Indicates that one entity bases its work, analysis, or decision on data or findings obtained from a particular survey conducted by another entity.
-
D.
coSurveyedWith
Indicates that two or more entities participated together in the same survey activity or data-collection effort.
-
E.
surveyed
Indicates that one entity systematically examined, questioned, or measured another entity or group to gather information or assess a situation.
- F. None of above. chosen
Provenance (4 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 6:28 a.m.