Triple
T3984314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake |
E86833
|
entity |
| Predicate | faregatesLocated |
P50326
|
FINISHED |
| Object | mezzanine |
—
|
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: mezzanine | Statement: [Lake, faregatesLocated, mezzanine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faregatesLocated Context triple: [Lake, faregatesLocated, mezzanine]
-
A.
faregates
chosen
Indicates a relationship where entities are associated with or pass through fare control gates, typically used to regulate and record entry or exit in a transit system.
-
B.
faregatesType
Indicates the type or category of faregates used for access control in a transit or similar system.
-
C.
fareControlLocation
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
-
D.
hasNearbyFerryPort
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
-
E.
hasNumberOfFerrySlips
Indicates the specific count of ferry slips associated with or available at a given entity.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.