Triple
T12296967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Where Did Our Love Go |
E293112
|
entity |
| Predicate | hasFootstomps |
P104324
|
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: [Where Did Our Love Go, hasFootstomps, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootstomps Context triple: [Where Did Our Love Go, hasFootstomps, yes]
-
A.
hasFootCrossing
Indicates that one entity has a designated crossing point specifically intended for pedestrians on foot.
-
B.
dropFeet
Indicates that an entity lowers or places its feet down, typically from a raised or suspended position.
-
C.
hasStandardToeCount
Indicates that an entity possesses the typical or expected number of toes for its kind.
-
D.
hasSettlementAtFoot
Indicates that a settlement is located at the base or lower slopes of a geographic feature such as a hill or mountain.
-
E.
hasPedestrianSteps
Indicates that one location or structure is connected to another by pedestrian steps or stairways.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:52 p.m.