Triple
T18354828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falling in Love Again |
E439760
|
entity |
| Predicate | hasAlternateLanguageVersion |
P2303
|
FINISHED |
| Object | German version |
—
|
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: German version | Statement: [Falling in Love Again, hasAlternateLanguageVersion, German version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateLanguageVersion Context triple: [Falling in Love Again, hasAlternateLanguageVersion, German version]
-
A.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
B.
hasSecondaryLanguage
Indicates that an entity possesses or uses a secondary language in addition to its primary language.
-
C.
hasAlternateTitleRegion
Indicates that an entity has an alternate title that is specifically used or valid within a particular geographic region.
-
D.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
E.
hasTranslation
chosen
Indicates that one entity is a translation or translated version of another entity in a different language.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516d458148190849ed28fa90eb92b |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.