Triple
T36832734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willowra |
E910186
|
entity |
| Predicate | hasTransportServices |
P201572
|
FINISHED |
| Object | periodic mail plane |
—
|
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: periodic mail plane | Statement: [Willowra, hasTransportServices, periodic mail plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportServices Context triple: [Willowra, hasTransportServices, periodic mail plane]
-
A.
hasTransitServiceType
Indicates that a transit service is associated with a specific type or category of service (e.g., bus, rail, express).
-
B.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
hasTransporters
Indicates that one entity possesses, provides, or is equipped with one or more means of transportation for another entity or purpose.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
| PDg | Predicate description generation | batch_6a00053cdcb08190980df73e235e9ad8 |
completed | May 10, 2026, 4:10 a.m. |
Created at: May 3, 2026, 4:13 p.m.