Triple
T5080778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Saints |
E114503
|
entity |
| Predicate | isCallAndResponse |
P56241
|
FINISHED |
| Object | often |
—
|
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: often | Statement: [The Saints, isCallAndResponse, often]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCallAndResponse Context triple: [The Saints, isCallAndResponse, often]
-
A.
hasCallAndResponseStructure
Indicates that one element initiates a call and another element provides a corresponding response, forming a paired, back-and-forth structural pattern.
-
B.
hasCallAndResponseVocals
chosen
Indicates that one entity produces vocalizations that are followed by corresponding or answering vocalizations from another entity.
-
C.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
D.
callsFor
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
E.
callType
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74f9d9848190919aad6cfe14f1cf |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.