Triple
T11474346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specialised Expos |
E271986
|
entity |
| Predicate | relativeDuration |
P75971
|
FINISHED |
| Object | shorter than Universal Expos |
—
|
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: shorter than Universal Expos | Statement: [Specialised Expos, relativeDuration, shorter than Universal Expos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeDuration Context triple: [Specialised Expos, relativeDuration, shorter than Universal Expos]
-
A.
durationUntil
Indicates the length of time remaining from a given starting point until a specified future event or state occurs.
-
B.
alternativeDuration
Indicates that there is an additional or substitute time span associated with an event or activity, differing from its primary or standard duration.
-
C.
laterDuration
Indicates that one event or time interval occurs after another and lasts for a specified duration.
-
D.
timeframeRelative
Indicates a temporal relationship where one event, state, or condition is positioned in time relative to another (e.g., before, after, or overlapping).
-
E.
timeIntervalLength
chosen
Indicates the duration or length of a specified time interval.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294c8dc48190a515f83c99405a3b |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.