Triple
T34203874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Rescue |
E877456
|
entity |
| Predicate | usesRescueTransporter |
P11571
|
FINISHED |
| Object | Thunderbird 2 |
—
|
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 2 | Statement: [International Rescue, usesRescueTransporter, Thunderbird 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRescueTransporter Context triple: [International Rescue, usesRescueTransporter, Thunderbird 2]
-
A.
usesTransport
chosen
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
B.
hasTransporters
Indicates that one entity possesses, provides, or is equipped with one or more means of transportation for another entity or purpose.
-
C.
usesAsCarrier
Indicates that one entity employs another entity as a carrier or medium for transporting or conveying something.
-
D.
inducesTransporter
Indicates that one entity causes or increases the activity or expression of a transporter in another entity or system.
-
E.
isTransport
Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:55 a.m.