Triple
T37124894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Brothers |
E919362
|
entity |
| Predicate | associatedEnsembleSection |
P47399
|
FINISHED |
| Object | “Four Brothers” saxophone section |
E1434126
|
NE 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: “Four Brothers” saxophone section | Statement: [Four Brothers, associatedEnsembleSection, “Four Brothers” saxophone section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEnsembleSection Context triple: [Four Brothers, associatedEnsembleSection, “Four Brothers” saxophone section]
-
A.
associatedEnsembleOf
Indicates that one entity is linked or connected to a particular ensemble, typically as a member, contributor, or related component of that group.
-
B.
associatedWithSection
chosen
Indicates that one entity is linked or connected to a particular section within a larger structure or context.
-
C.
associatedWorkSection
Indicates that one work or resource is related to a specific section or part of another work.
-
D.
usesSectionOf
Indicates that one entity makes use of a specific section or part of another entity.
-
E.
associatedPrayerBookSection
Indicates a relationship where a prayer or liturgical element is linked to a specific section within a prayer book.
- F. None of above.
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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f6a1daee08190a554b74428cf581b |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.