Triple
T31923670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Robert E. Peary |
E815039
|
entity |
| Predicate | constructionStartToLaunchDuration |
P3543
|
FINISHED |
| Object | under 5 days |
—
|
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: under 5 days | Statement: [SS Robert E. Peary, constructionStartToLaunchDuration, under 5 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionStartToLaunchDuration Context triple: [SS Robert E. Peary, constructionStartToLaunchDuration, under 5 days]
-
A.
constructionTime
chosen
Indicates the duration or specific point in time required to construct or build an entity.
-
B.
constructionStartAfter
Indicates that the start of one construction activity or project occurs after the start of another specified construction activity or project.
-
C.
endConstructionTime
Indicates the point in time at which a construction process or building activity is completed.
-
D.
startOfConstructionApprox
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
-
E.
growthDuration
Indicates the length of time over which a growth process or development occurs.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 12:03 a.m.