Triple
T27744628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo battlefield |
E701944
|
entity |
| Predicate | yearLionMoundCompleted |
P104624
|
FINISHED |
| Object | 1826 |
—
|
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: 1826 | Statement: [Waterloo battlefield, yearLionMoundCompleted, 1826]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearLionMoundCompleted Context triple: [Waterloo battlefield, yearLionMoundCompleted, 1826]
-
A.
archaeologicalMoundName
Indicates the specific name assigned to an archaeological mound in which something is located, associated, or from which it originates.
-
B.
yearOfMonument
chosen
Indicates the specific year in which a monument was established, built, or officially dedicated.
-
C.
dateOfMainRoyalMonument
Indicates the date on which a person's principal royal monument (such as a main tomb or commemorative structure) was established, completed, or formally dedicated.
-
D.
includedInMonumentYear
Indicates that an entity was incorporated into or recognized as part of a monument in a specific year.
-
E.
sarcophagusCompletionDate
Indicates the date on which the construction or finishing of a sarcophagus was completed.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63719b84c81909c805036f6717239 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:15 p.m.