Triple
T29873562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santos-Dumont No. 6 dirigible |
E758657
|
entity |
| Predicate | achievementTimeLimit |
P22110
|
FINISHED |
| Object | 30 minutes |
—
|
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: 30 minutes | Statement: [Santos-Dumont No. 6 dirigible, achievementTimeLimit, 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievementTimeLimit Context triple: [Santos-Dumont No. 6 dirigible, achievementTimeLimit, 30 minutes]
-
A.
achievementTiming
Indicates the temporal relationship specifying when an achievement occurs or is attained relative to other events or a reference time.
-
B.
timeLimited
chosen
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
C.
airedUntil
Indicates the date or time up to which something, typically a broadcast or series, was shown or transmitted.
-
D.
goalTimeRecord
Indicates that a specific time value is recorded as the target or goal duration for an activity or process.
-
E.
achievementScope
Indicates the extent or domain within which an achievement is recognized, measured, or considered valid.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676c8ab448190900f6f8984e105a2 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 5:54 p.m.