Triple
T34101283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnniac computer |
E874574
|
entity |
| Predicate | yearFirstOperational |
P178233
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [Johnniac computer, yearFirstOperational, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearFirstOperational Context triple: [Johnniac computer, yearFirstOperational, 1953]
-
A.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
B.
firstOperationalCrewFlightYear
Indicates the year in which the first operational crewed flight associated with the subject took place.
-
C.
yearFirstDelivered
Indicates the calendar year in which something (such as a product, service, or item) was first delivered or made available.
-
D.
aircraftEnteredServiceWith
Indicates that an aircraft began its operational service or was officially introduced into use with a specified operator, organization, or context.
-
E.
firstCrewedTestFlightYear
Indicates the calendar year in which an entity conducted its first test flight involving a human crew.
- F. None of above. chosen
Provenance (4 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c692af8819084489cd50607ca1b |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:53 a.m.