Triple
T21678643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mockingbird |
E535040
|
entity |
| Predicate | hasCallAndResponsePattern |
P22739
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mockingbird, hasCallAndResponsePattern, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallAndResponsePattern Context triple: [Mockingbird, hasCallAndResponsePattern, true]
-
A.
hasCallAndResponseStructure
chosen
Indicates that one element initiates a call and another element provides a corresponding response, forming a paired, back-and-forth structural pattern.
-
B.
hasCall
Indicates that one entity initiates or participates in a telephone or voice communication with another entity.
-
C.
hasCallingConvention
Indicates that a function or method uses a specific calling convention that defines how arguments are passed and results are returned.
-
D.
hasResponderMessageCount
Indicates the number of messages sent by the responder in a given interaction or conversation.
-
E.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a11088081908911af2629f54c1c |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:43 p.m.