Triple
T26157261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fearn |
E659997
|
entity |
| Predicate | hasHistoricGraveyard |
P178756
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fearn, hasHistoricGraveyard, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricGraveyard Context triple: [Fearn, hasHistoricGraveyard, true]
-
A.
hasHistoricGround
Indicates that one entity is located on, associated with, or includes land or grounds of historical significance related to another entity.
-
B.
hasHistoricGate
Indicates that an entity possesses or is associated with a historically significant gate or gateway structure.
-
C.
hasHistoricTerminal
Indicates that an entity possesses or is associated with a historically significant terminal facility or endpoint.
-
D.
hasHistoricGreen
Indicates that an entity possesses or is associated with a historically significant green-colored feature, area, or designation.
-
E.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 26, 2026, 8:28 p.m.