Triple
T30178299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santos-Dumont No. 4 |
E767123
|
entity |
| Predicate | developedAtTime |
P118762
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Santos-Dumont No. 4, developedAtTime, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAtTime Context triple: [Santos-Dumont No. 4, developedAtTime, early 20th century]
-
A.
developedAt
Indicates the place or location where something was created, built, or developed.
-
B.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
C.
developmentDate
chosen
Indicates the date on which something was created, developed, or brought into existence.
-
D.
developedAround
Indicates that one entity was created, designed, or evolved with the other entity as its central focus, basis, or surrounding context.
-
E.
developedOverPeriod
Indicates that something was created, expanded, or progressed continuously throughout a specified span of time.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 7:25 p.m.