Triple
T28914549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libertà, Odio, Vendetta, Eternità |
E733320
|
entity |
| Predicate | formsAcronym |
P42398
|
FINISHED |
| Object | LOVE |
—
|
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: LOVE | Statement: [Libertà, Odio, Vendetta, Eternità, formsAcronym, LOVE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsAcronym Context triple: [Libertà, Odio, Vendetta, Eternità, formsAcronym, LOVE]
-
A.
acronymExpansion
chosen
Indicates that one term is an acronym whose letters stand for the words in another, longer expression.
-
B.
nameAcronymComment
Indicates that an explanatory comment describes or clarifies the relationship between a full name and its corresponding acronym.
-
C.
acronymContext
Indicates that one term is used as an acronym specifically within the contextual scope defined by another entity (such as a document, domain, or usage setting).
-
D.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
-
E.
acronymOfCreatedProgram
Indicates that one entity is the acronym or abbreviated name of a program that was created or developed as represented by the other entity.
- 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_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 8:13 a.m.