Triple
T31531249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Step Inside Love |
E804485
|
entity |
| Predicate | hasDemoRecordingLocation |
P196596
|
FINISHED |
| Object | London |
—
|
NE NERFINISHED |
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: London | Statement: [Step Inside Love, hasDemoRecordingLocation, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemoRecordingLocation Context triple: [Step Inside Love, hasDemoRecordingLocation, London]
-
A.
hasDemonstration
Indicates that one entity includes, is accompanied by, or is associated with a demonstration or illustrative example of another entity or concept.
-
B.
hasAcousticDemoVersion
Indicates that an entity has a version or recording presented in an acoustic demo form.
-
C.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
D.
hasTrialLocation
Indicates that a trial or legal proceeding takes place at, or is associated with, a specific location.
-
E.
hasDigitalRecordingCapabilities
Indicates that an entity possesses the ability to create, store, or process information in digital recording form.
- F. None of above. chosen
Provenance (4 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
| PDg | Predicate description generation | batch_69fe5d580d7c819097cb18d438b01d08 |
completed | May 8, 2026, 10:02 p.m. |
Created at: April 30, 2026, 10:01 p.m.