Triple
T24268493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Gibbs the Mighty Two |
E604909
|
entity |
| Predicate | usedStudioBand |
P53870
|
FINISHED |
| Object | The Professionals |
—
|
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: The Professionals | Statement: [Joe Gibbs the Mighty Two, usedStudioBand, The Professionals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedStudioBand Context triple: [Joe Gibbs the Mighty Two, usedStudioBand, The Professionals]
-
A.
usedAsStudioBy
Indicates that a place or facility functions as a studio space utilized by a particular person or organization.
-
B.
usesStudioEffects
Indicates that an entity incorporates studio-produced effects (such as audio or visual enhancements) in the creation or presentation of its work.
-
C.
recordingBandFor
Indicates that a particular musical band is responsible for recording a given musical work, track, or album.
-
D.
usesBand
chosen
Indicates that one entity employs or makes use of a particular band (such as a group, frequency band, or band resource) in performing an action or fulfilling a function.
-
E.
hasRecordingStudio
Indicates that an entity possesses, operates, or is associated with a recording studio.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5736a08190a1f958ebf18302f9 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.