Triple
T29682864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Point ferry terminal |
E751001
|
entity |
| Predicate | hasCheckInLanes |
P188884
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Duke Point ferry terminal, hasCheckInLanes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInLanes Context triple: [Duke Point ferry terminal, hasCheckInLanes, yes]
-
A.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
B.
hasFreeLanes
Indicates that a route, road, or pathway currently has lanes available that are not occupied or congested.
-
C.
hasLaneConfigurations
Indicates that an entity is associated with one or more specific arrangements or patterns of lanes (e.g., number, type, or direction of lanes).
-
D.
hasTrackLanes
Indicates that an entity (such as a road or track) includes one or more designated lanes for vehicle or train movement.
-
E.
hasCheckInCounters
Indicates that an entity is associated with one or more check-in counters used for processing arrivals or registrations.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: April 28, 2026, 7:11 p.m.