Triple
T23679176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing (first stage) |
E584969
|
entity |
| Predicate | workedOnVehicle |
P30363
|
FINISHED |
| Object | Saturn V |
—
|
NE NERFINISHED |
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: Saturn V | Statement: [Boeing (first stage), workedOnVehicle, Saturn V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedOnVehicle Context triple: [Boeing (first stage), workedOnVehicle, Saturn V]
-
A.
workOn
chosen
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
B.
hasVehicleService
Indicates that one entity provides, performs, or is responsible for vehicle-related services for another entity.
-
C.
materialWorked
Indicates that an agent performs work or processing on a specified material.
-
D.
associatedWithMechanic
Indicates a relationship where an entity is connected or linked to a mechanic, such as a process, rule, or functional mechanism involved in its operation or behavior.
-
E.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f5a7b48190b93d27416003e173 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.