Triple
T8966348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ennio Morricone |
E214143
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ennio |
E214143
|
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: Ennio | Statement: [Ennio Morricone, givenName, Ennio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ennio Context triple: [Ennio Morricone, givenName, Ennio]
-
A.
Ennio
chosen
Ennio is an Italian given name most famously associated with the renowned film composer Ennio Morricone.
-
B.
Marcello
Marcello is a masculine given name of Italian origin, commonly used in Italy and other Romance-language countries.
-
C.
Enrico
Enrico is the given name of Enrico Fermi, the renowned Italian-American physicist who helped develop the first nuclear reactor and made foundational contributions to quantum theory and nuclear physics.
-
D.
Luciano
Luciano is a masculine given name of Italian origin, famously borne by the renowned operatic tenor Luciano Pavarotti.
-
E.
Gianni
Gianni is an Italian given name commonly used for men, often as a diminutive of Giovanni.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67623818819096aee155a9b43e8f |
completed | April 1, 2026, 12:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc95879c08190b0091548c8c00207 |
completed | April 3, 2026, 2:06 p.m. |
Created at: March 30, 2026, 7:01 p.m.