Triple
T667086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annecy Round (1949) |
E12887
|
entity |
| Predicate | isPostwarRound |
P18094
|
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: [Annecy Round (1949), isPostwarRound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPostwarRound Context triple: [Annecy Round (1949), isPostwarRound, true]
-
A.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
B.
hasProperRounds
Indicates that an entity is associated with rounds that meet specified standards or criteria for being considered proper or valid.
-
C.
wartimeControl
Indicates that one entity exercises authoritative command or governance over another entity specifically during a period of armed conflict or war.
-
D.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
E.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff7ca788190bef58ce46849b9d0 |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49fcf0cb4819096edea4037ca2c03 |
completed | March 1, 2026, 8:21 p.m. |
Created at: March 1, 2026, 7:36 p.m.