Triple
T36567199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Images, Book I |
E902010
|
entity |
| Predicate | thirdPiece |
P62307
|
FINISHED |
| Object | Mouvement |
—
|
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: Mouvement | Statement: [Images, Book I, thirdPiece, Mouvement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdPiece Context triple: [Images, Book I, thirdPiece, Mouvement]
-
A.
thirdElement
chosen
Indicates that one entity is the third element in an ordered sequence or tuple associated with another entity.
-
B.
thirdSingle
Indicates that an entity is the third single (e.g., third single release) associated with another entity, typically in a sequence such as from an album or artist.
-
C.
thirdWord
Indicates that one entity is the third word in sequence within another entity (such as a text or phrase).
-
D.
thirdEpisode
Indicates that one entity is the third episode in sequence within a series or season relative to another entity.
-
E.
thirdFactor
Indicates that an entity serves as the third factor or element in a multi-factor relationship, typically complementing two other primary factors in a given context.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:11 p.m.