Triple
T25623573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilsede |
E642365
|
entity |
| Predicate | accessByCar |
P147666
|
FINISHED |
| Object | not directly accessible to visitors by private car |
—
|
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: not directly accessible to visitors by private car | Statement: [Wilsede, accessByCar, not directly accessible to visitors by private car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessByCar Context triple: [Wilsede, accessByCar, not directly accessible to visitors by private car]
-
A.
transportAccessType
chosen
Indicates the type or mode of transportation access available or used in a given context.
-
B.
vehicleAccess
Indicates that one entity is permitted to use, enter, or otherwise access a particular vehicle.
-
C.
hasVehicleAccess
Indicates that an entity is permitted to use or enter a particular vehicle.
-
D.
hasPrimaryVehicularAccessTo
Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
-
E.
hasMotorVehicleAccess
Indicates that an entity is permitted to use or operate a motor vehicle within a specified area, context, or under certain conditions.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 5:06 p.m.