Triple
T14567818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esch-sur-Sûre |
E341831
|
entity |
| Predicate | castleFirstMentioned |
P114704
|
FINISHED |
| Object | 10th century (approximate) |
—
|
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: 10th century (approximate) | Statement: [Esch-sur-Sûre, castleFirstMentioned, 10th century (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castleFirstMentioned Context triple: [Esch-sur-Sûre, castleFirstMentioned, 10th century (approximate)]
-
A.
originalCastleFoundedIn
Indicates the specific year or time period when the original version of a castle was first established or built.
-
B.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
C.
castleName
Indicates that an entity has the specified name of a castle.
-
D.
originalCastleFoundedBy
Indicates that an original castle was established or created by a specific person, group, or authority.
-
E.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38d89fc819086709fd3607b835f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:23 a.m.