Triple
T31311532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Childeric I |
E798475
|
entity |
| Predicate | graveDiscoveredIn |
P3985
|
FINISHED |
| Object | Tournai |
E75623
|
NE 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: Tournai | Statement: [Childeric I, graveDiscoveredIn, Tournai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graveDiscoveredIn Context triple: [Childeric I, graveDiscoveredIn, Tournai]
-
A.
tombDiscovered
Indicates that a tomb has been found or uncovered, typically as the result of exploration, excavation, or chance discovery.
-
B.
discoveredRemainsIn
Indicates that one entity found or uncovered the physical remains of another entity at a specific location.
-
C.
discoveryOfRemainsDate
Indicates the date on which the remains were discovered.
-
D.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
E.
wasDiscoveredAt
chosen
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
- F. None of above.
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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b075df4a481909286f36d0448b8a3 |
completed | June 11, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:15 p.m.