Triple
T8119043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Look At You |
E189555
|
entity |
| Predicate | hasMatureSoundComparedTo |
P81371
|
FINISHED |
| Object | Friday |
—
|
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: Friday | Statement: [Look At You, hasMatureSoundComparedTo, Friday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatureSoundComparedTo Context triple: [Look At You, hasMatureSoundComparedTo, Friday]
-
A.
hasMatureSound
Indicates that an entity produces or is associated with a sound quality characteristic of adulthood or full development, as opposed to a youthful or immature sound.
-
B.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
hasMaturity
Indicates that an entity possesses a specified level, state, or stage of development or maturity.
-
D.
hasHeavierSoundThan
Indicates that one entity produces or is associated with a sound that is sonically heavier, more intense, or more forceful than that of another entity.
-
E.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound of another entity.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:33 p.m.