Triple
T34203871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Rescue |
E877456
|
entity |
| Predicate | usesCommunicationFacility |
P59911
|
FINISHED |
| Object | Thunderbird 5 |
—
|
NE NERFINISHED |
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: Thunderbird 5 | Statement: [International Rescue, usesCommunicationFacility, Thunderbird 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommunicationFacility Context triple: [International Rescue, usesCommunicationFacility, Thunderbird 5]
-
A.
usesTelecommunications
Indicates that one entity communicates with or transmits information to another by means of telecommunications technologies or networks.
-
B.
usedToCommunicate
chosen
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
C.
hasCommunicationUse
Indicates that something is used for, or serves the purpose of, communication.
-
D.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
E.
enablesCommunicationWith
Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 1:55 a.m.