Triple
T15361596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawrence University |
E367300
|
entity |
| Predicate | hasMusicEnsemble |
P55033
|
FINISHED |
| Object | orchestras |
—
|
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: orchestras | Statement: [Lawrence University, hasMusicEnsemble, orchestras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicEnsemble Context triple: [Lawrence University, hasMusicEnsemble, orchestras]
-
A.
hasMusicalEnsemble
chosen
Indicates that one entity is associated with or includes a particular musical ensemble (such as a band, orchestra, or group) as part of its activities or composition.
-
B.
hasMusicalEnsembleType
Indicates that an entity is associated with or classified as a particular type of musical ensemble.
-
C.
usesMusicEnsemble
Indicates that one entity employs or incorporates a particular music ensemble in carrying out an action, function, or production.
-
D.
hasMusicalEnsembleGenre
Indicates that a musical ensemble is associated with or performs in a particular musical genre.
-
E.
hasEnsembles
Indicates that an entity is associated with one or more ensembles, typically as a member, component, or participant.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4607408190ab281a7f7a8012d3 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.