Triple
T25482190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune's Staircase |
E638604
|
entity |
| Predicate | hasApproximateTransitTime |
P125927
|
FINISHED |
| Object | about 90 minutes for a boat |
—
|
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: about 90 minutes for a boat | Statement: [Neptune's Staircase, hasApproximateTransitTime, about 90 minutes for a boat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateTransitTime Context triple: [Neptune's Staircase, hasApproximateTransitTime, about 90 minutes for a boat]
-
A.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
B.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
C.
hasApproximateWalkingTimeTo
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
D.
timeframeApproximate
chosen
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
-
E.
areEstimatedIn
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 2:31 p.m.