Triple

T36567301
Position Surface form Disambiguated ID Type / Status
Subject Act IV E902012 entity
Predicate hasWorkTitle P3254 FINISHED
Object Acte IV (French title)
Acte IV is the French title of the fourth act of a theatrical or operatic work, typically marking a key stage in the development or resolution of its plot.
E2189066 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: Acte IV (French title) | Statement: [Act IV, hasWorkTitle, Acte IV (French title)]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Acte IV (French title)
Triple: [Act IV, hasWorkTitle, Acte IV (French title)]
Generated description
Acte IV is the French title of the fourth act of a theatrical or operatic work, typically marking a key stage in the development or resolution of its plot.

Provenance (5 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_69f7c280af18819083b9010d13b2181e completed May 3, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39e6f86a2881908e83d030af707303 completed June 23, 2026, 1:52 a.m.
NEDg Description generation batch_6a39e781b60881908c02a333187588f9 completed June 23, 2026, 1:55 a.m.
NED2 Entity disambiguation (via description) batch_6a39ebb78b44819084252f4b2cefe4e6 completed June 23, 2026, 2:13 a.m.
Created at: May 3, 2026, 4:11 p.m.