Triple
T31074828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Flame of Love |
E791926
|
entity |
| Predicate | isMultilingualVersion |
P77676
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Flame of Love, isMultilingualVersion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultilingualVersion Context triple: [The Flame of Love, isMultilingualVersion, true]
-
A.
isMultilingual
chosen
Indicates that an entity can understand and/or communicate in multiple languages.
-
B.
hasBilingualVersions
Indicates that something exists in two different language versions or forms.
-
C.
hasMultilingualPresence
Indicates that an entity maintains an active presence or representation in multiple languages.
-
D.
isMultilingualWithinChinese
Indicates that an entity uses or involves multiple distinct Chinese language varieties (e.g., dialects, scripts, or regional forms) within a Chinese linguistic context.
-
E.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695b877c08190b6548da71d27dde7 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.