Triple
T6682609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Harbour Bridge Climb |
E152019
|
entity |
| Predicate | hasTimeOptions |
P71724
|
FINISHED |
| Object | day climbs |
—
|
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: day climbs | Statement: [Sydney Harbour Bridge Climb, hasTimeOptions, day climbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeOptions Context triple: [Sydney Harbour Bridge Climb, hasTimeOptions, day climbs]
-
A.
hasCutoffTime
Indicates that there is a specific time limit or deadline by which an action, event, or process must be completed or initiated.
-
B.
hasTimeOfDay
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
-
C.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
D.
hasTimeDimension
Indicates that something possesses or is associated with a temporal aspect, such as duration, point in time, or time-based variation.
-
E.
hasTimeOffset
Indicates that one temporal value is shifted or displaced from another by a specified amount of time.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c0aa8c5c8190a302b261f11b70cb |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0b6d00819086205b8ce30dd045 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6c0a90a088190978061cb05dbe268 |
completed | March 27, 2026, 5:38 p.m. |
Created at: March 27, 2026, 2:04 p.m.