Triple
T3677059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There Goes My Baby |
E78017
|
entity |
| Predicate | hasOrchestrationFeature |
P35077
|
FINISHED |
| Object | strings |
—
|
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: strings | Statement: [There Goes My Baby, hasOrchestrationFeature, strings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrchestrationFeature Context triple: [There Goes My Baby, hasOrchestrationFeature, strings]
-
A.
hasOrchestrationBy
Indicates that something is organized, coordinated, or arranged by a specified agent or entity.
-
B.
hasOrchestralFeature
chosen
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
-
C.
featuresOrchestrationBy
Indicates that something (such as a work, event, or performance) is characterized by or includes orchestration carried out by a particular agent or entity.
-
D.
orchestratedFor
Indicates that one entity planned, coordinated, or arranged something specifically on behalf of or for the benefit of another entity.
-
E.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4643cf08190b2d10ddf4aac7407 |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.