Triple
T3234442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rocket |
E67817
|
entity |
| Predicate | originalUseStart |
P33743
|
FINISHED |
| Object | 1830 |
—
|
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: 1830 | Statement: [The Rocket, originalUseStart, 1830]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalUseStart Context triple: [The Rocket, originalUseStart, 1830]
-
A.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
B.
firstUsedBy
Indicates that something was initially utilized, applied, or employed by a particular entity before any others.
-
C.
startUseBy
chosen
Indicates the point in time from which an entity begins to be used by another entity or for a particular purpose.
-
D.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaedcd9588190b3623f0109d653a4 |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.