Triple
T28914559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libertà, Odio, Vendetta, Eternità |
E733320
|
entity |
| Predicate | hasInitialismLetter2 |
P17387
|
FINISHED |
| Object | O |
—
|
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: O | Statement: [Libertà, Odio, Vendetta, Eternità, hasInitialismLetter2, O]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInitialismLetter2 Context triple: [Libertà, Odio, Vendetta, Eternità, hasInitialismLetter2, O]
-
A.
hasInitialLetters
Indicates that one entity’s initial letters or acronym are derived from or correspond to the other entity.
-
B.
usesInitialsAndFinals
Indicates that the entity represents or expresses something by combining initial components with final components (such as initials with finals in a phonetic or naming system).
-
C.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
-
D.
secondLetterMatches
Indicates that the second character of one string or sequence is the same as the second character of another string or sequence.
-
E.
hasLetter
chosen
Indicates that one entity contains, includes, or is associated with a specific letter or character.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 28, 2026, 8:13 a.m.