Triple
T18654684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert I of Dreux |
E456027
|
entity |
| Predicate | houseFoundedIn |
P18074
|
FINISHED |
| Object | 12th century |
—
|
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: 12th century | Statement: [Robert I of Dreux, houseFoundedIn, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseFoundedIn Context triple: [Robert I of Dreux, houseFoundedIn, 12th century]
-
A.
houseFounded
chosen
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
B.
houseFoundedFrom
Indicates that a house, organization, or lineage was established or originated from a specified source, predecessor, or founding entity.
-
C.
birthHouseBuiltBy
Indicates that the house in which a person was born was constructed by a specified builder or entity.
-
D.
houseFoundedLaterAssociatedWith
Indicates that one house or household was established after another and is subsequently associated or linked to that earlier house in some way.
-
E.
placeBuilt
Indicates that a structure or facility was constructed at a specific location.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55084012881909b9dd60565011c86 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.