Triple
T14288826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papunya |
E354252
|
entity |
| Predicate | transportOptions |
P113640
|
FINISHED |
| Object | 4WD access common |
—
|
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: 4WD access common | Statement: [Papunya, transportOptions, 4WD access common]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportOptions Context triple: [Papunya, transportOptions, 4WD access common]
-
A.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transportFor
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
-
C.
transportHubType
Indicates the specific category or kind of transport hub associated with an entity (e.g., airport, train station, bus terminal).
-
D.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
E.
transportModeIntegration
Indicates that different modes of transportation are coordinated or combined to enable seamless or efficient movement within a journey or transport system.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de698023288190b1d705235c2b2ca3 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.