Triple
T15530623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Amos |
E370204
|
entity |
| Predicate | hasApproximateReturnTime |
P4874
|
FINISHED |
| Object | 3–4 hours |
—
|
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: 3–4 hours | Statement: [Mount Amos, hasApproximateReturnTime, 3–4 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateReturnTime Context triple: [Mount Amos, hasApproximateReturnTime, 3–4 hours]
-
A.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
B.
hasApproximateDuration
chosen
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
C.
timeOfReturn
Indicates the specific time at which an entity comes back to a prior location or state.
-
D.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
E.
hasApproximateTransport
Indicates that one entity is connected to another by a transport option whose route, timing, or characteristics are similar to, but not exactly the same as, a referenced or ideal transport connection.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414773548190b3311515f9d957dd |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:06 a.m.