Triple
T27747911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ge 4/4 III |
E702036
|
entity |
| Predicate | firstUnitDelivered |
P110547
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Ge 4/4 III, firstUnitDelivered, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUnitDelivered Context triple: [Ge 4/4 III, firstUnitDelivered, 1993]
-
A.
launchedFirstUnit
Indicates that one entity initiated and deployed the first unit of something (e.g., product, system, or mission) before any others.
-
B.
commissionedFirstUnit
Indicates that one entity formally brought the first operational unit of another entity into active service or use.
-
C.
firstShippedOn
chosen
Indicates the date on which something was initially shipped or dispatched for the first time.
-
D.
firstDeployedIn
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
-
E.
firstProducedAt
Indicates the location or context where something was originally created, manufactured, or brought into existence for the first 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: April 27, 2026, 4:18 p.m.