Triple
T29104839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagledale Ferry Dock site |
E736733
|
entity |
| Predicate | hasMarkerType |
P2130
|
FINISHED |
| Object | historic marker |
—
|
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: historic marker | Statement: [Eagledale Ferry Dock site, hasMarkerType, historic marker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarkerType Context triple: [Eagledale Ferry Dock site, hasMarkerType, historic marker]
-
A.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
B.
hasBorderMarkerType
Indicates that a border marker possesses or is classified by a specific type or category of border marker.
-
C.
hasNonManualMarkers
Indicates that a sign or gesture is accompanied by specific non-manual features (such as facial expressions, head or body movements) that contribute to its grammatical or semantic meaning.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: April 28, 2026, 11:14 a.m.