Triple
T13858234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timbertop campus |
E333118
|
entity |
| Predicate | isBoardingOnly |
P111835
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Timbertop campus, isBoardingOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBoardingOnly Context triple: [Timbertop campus, isBoardingOnly, true]
-
A.
isBoarding
Indicates that an entity is in the process of getting onto or entering a vehicle, vessel, or similar mode of transport.
-
B.
hasBoardingType
Indicates the specific manner or method by which an entity is boarded or accessed (e.g., how passengers or items are taken on).
-
C.
isPassengerOnly
Indicates that the subject entity is restricted to passenger use only and does not accommodate cargo, freight, or mixed-use purposes.
-
D.
hasBoardingOption
Indicates that an entity offers or is associated with a particular way or method by which passengers or items can board or be taken on.
-
E.
hasPassengerOnlyService
Indicates that the service provided involves only the transportation of passengers, with no freight or cargo component.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:14 p.m.