Triple
T34344398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Fairbanks |
E881388
|
entity |
| Predicate | usesTransportationForMinistry |
P11571
|
FINISHED |
| Object | bush planes |
—
|
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: bush planes | Statement: [Diocese of Fairbanks, usesTransportationForMinistry, bush planes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTransportationForMinistry Context triple: [Diocese of Fairbanks, usesTransportationForMinistry, bush planes]
-
A.
usesTransportNetwork
Indicates that an entity makes use of a transport network (such as roads, rail, or transit systems) to move people, goods, or services.
-
B.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
C.
usesTransport
chosen
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
D.
hasPublicTransportUsage
Indicates that an entity makes use of, or is associated with the use of, public transportation services.
-
E.
passesUsedForTransportation
Indicates that the passes are utilized as a means or instrument for transporting people or goods.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 1:58 a.m.