Triple
T26947607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billina |
E678688
|
entity |
| Predicate | gainsSpeechReason |
P161992
|
FINISHED |
| Object | being in a fairyland gives her the power of speech |
—
|
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: being in a fairyland gives her the power of speech | Statement: [Billina, gainsSpeechReason, being in a fairyland gives her the power of speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainsSpeechReason Context triple: [Billina, gainsSpeechReason, being in a fairyland gives her the power of speech]
-
A.
gainsSpeechIn
Indicates that an entity acquires or develops the ability to speak within a specified context, time, or location.
-
B.
givesSpeechOn
Indicates that one entity delivers or presents a speech whose topic or subject matter concerns another entity.
-
C.
givesSpeechTo
Indicates that one entity delivers a speech or formal address directed toward another entity or audience.
-
D.
givesSpeechIn
Indicates that an entity delivers or presents a speech within a particular location, event, or context.
-
E.
regainedSpeech
Indicates that an entity has recovered the ability to speak after having previously lost it.
- F. None of above. chosen
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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62086a0488190a5ba24fdca774cd5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 6:22 a.m.