Triple
T5053238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crazy in the Night (Barking at Airplanes) |
E113835
|
entity |
| Predicate | hasChorusDescription |
P60898
|
FINISHED |
| Object | known for its catchy chorus |
—
|
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: known for its catchy chorus | Statement: [Crazy in the Night (Barking at Airplanes), hasChorusDescription, known for its catchy chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChorusDescription Context triple: [Crazy in the Night (Barking at Airplanes), hasChorusDescription, known for its catchy chorus]
-
A.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
B.
hasChorusBy
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
C.
hasChorusSample
Indicates that one musical work incorporates a sampled portion of the chorus from another work.
-
D.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
-
E.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd742a59448190918766c261cfa13d |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:38 p.m.