Triple
T23568799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Explorers |
E580042
|
entity |
| Predicate | roleInASeaSymphony |
P24740
|
FINISHED |
| Object | final movement text |
—
|
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: final movement text | Statement: [The Explorers, roleInASeaSymphony, final movement text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInASeaSymphony Context triple: [The Explorers, roleInASeaSymphony, final movement text]
-
A.
musicalEnsembleRole
Indicates the specific function or position an individual holds within a musical ensemble, such as performer, conductor, or composer.
-
B.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
coastRole
Indicates a role or function that an entity has specifically in relation to a coast or coastal area.
-
E.
roleInSEALABII
Indicates that an entity has a specific role or position in the context of SEALAB II.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd15ca48190afd119ec1b4a07b2 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:35 p.m.