Triple
T10033501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Only Love |
E204905
|
entity |
| Predicate | hasPerformerLanguage |
P43093
|
FINISHED |
| Object | Greek |
—
|
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: Greek | Statement: [Only Love, hasPerformerLanguage, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerLanguage Context triple: [Only Love, hasPerformerLanguage, Greek]
-
A.
performedLanguage
chosen
Indicates that an action, work, or performance was carried out using a specified language.
-
B.
repertoireLanguage
Indicates that the associated entity’s repertoire (e.g., works, performances, or outputs) is expressed or available in a particular language.
-
C.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
D.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
E.
hasMemberLanguage
Indicates that one entity is a language that is a constituent or member of a larger language group, family, or collection 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce490ff08190963d841b05d150a7 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.