Triple
T982621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mason–Dixon Line |
E21202
|
entity |
| Predicate | markedBy |
P2130
|
FINISHED |
| Object | stone markers |
—
|
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: stone markers | Statement: [Mason–Dixon Line, markedBy, stone markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: markedBy Context triple: [Mason–Dixon Line, markedBy, stone markers]
-
A.
markType
Indicates the specific category or kind of mark associated with or applied to an entity.
-
B.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
-
C.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
D.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
mintMarkUsedOn
Indicates that a particular mint mark was applied to or appears on a specific coin or numismatic item.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b49284ac8190b1d7c828d728893c |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.