Triple
T2582192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convair T-29 |
E57116
|
entity |
| Predicate | enteredServiceAsTrainer |
P2339
|
FINISHED |
| Object | late 1940s |
—
|
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: late 1940s | Statement: [Convair T-29, enteredServiceAsTrainer, late 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceAsTrainer Context triple: [Convair T-29, enteredServiceAsTrainer, late 1940s]
-
A.
trainingPartner
Indicates that two entities participate together in training activities, typically collaborating or assisting each other in practice or skill development.
-
B.
beganUnderCoach
Indicates that one entity started its activity, career, or involvement while being coached or supervised by another entity.
-
C.
basedInAsCoach
Indicates that a person holds a coaching position for an organization or team that is located in a specified place.
-
D.
enteredService
chosen
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
E.
trainingSystem
Indicates a system or framework used to train, instruct, or develop skills or knowledge in a target entity.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3c843bc8190837cea3441bf3ca1 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.