Triple
T26755285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Night in Bangkok |
E674652
|
entity |
| Predicate | hasSpokenVerses |
P98558
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [One Night in Bangkok, hasSpokenVerses, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpokenVerses Context triple: [One Night in Bangkok, hasSpokenVerses, Yes]
-
A.
hasSpokenWordVerses
chosen
Indicates that an entity (such as a work or recording) contains or features verses performed in spoken word form.
-
B.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
C.
hasSpokenWordIntro
Indicates that an entity includes or features an introductory segment performed in spoken word form.
-
D.
hasSpokenStandard
Indicates that an entity has spoken using a recognized standard form of a language (e.g., standard dialect or official register).
-
E.
hasLiveSpokenIntroductions
Indicates that one entity provides live, spoken introductory remarks or presentations for another entity or event.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 3:55 a.m.