Triple
T30622444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Come On In the Room |
E779484
|
entity |
| Predicate | hasCallAndResponseLeader |
P29274
|
FINISHED |
| Object | choir leader |
—
|
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: choir leader | Statement: [Come On In the Room, hasCallAndResponseLeader, choir leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallAndResponseLeader Context triple: [Come On In the Room, hasCallAndResponseLeader, choir leader]
-
A.
hasLeaderParticipant
chosen
Indicates that an entity participates in an event or activity in the role of a leader.
-
B.
hasCallAndResponseStructure
Indicates that one element initiates a call and another element provides a corresponding response, forming a paired, back-and-forth structural pattern.
-
C.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
D.
hasLeaderAtLocation
Indicates that a specified leader is associated with or holds leadership responsibilities at a particular location.
-
E.
hasSuccessorLeader
Indicates that one leader directly follows another in a position of authority or leadership role.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 29, 2026, 8:27 p.m.