Triple
T30679128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hair (film choreography) |
E781003
|
entity |
| Predicate | featuresSongSequence |
P41558
|
FINISHED |
| Object | Aquarius |
—
|
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: Aquarius | Statement: [Hair (film choreography), featuresSongSequence, Aquarius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSongSequence Context triple: [Hair (film choreography), featuresSongSequence, Aquarius]
-
A.
featuresSongFrom
Indicates that one musical work includes or incorporates a song originating from another source.
-
B.
appearsInSongSequence
Indicates that one entity is featured or present within the sequence of elements that make up a particular song.
-
C.
featuresSequence
chosen
Indicates that one entity presents or contains another entity as an ordered sequence of features or elements.
-
D.
featuresSongAbout
Indicates that one entity includes or presents a song whose subject or content is about another entity.
-
E.
featuresReRecordedSong
Indicates that an entity (such as an album, release, or performance) includes a song that has been recorded again in a new version distinct from its original recording.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 29, 2026, 8:32 p.m.