Triple
T36169838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Apollo Program Office |
E1046114
|
entity |
| Predicate | usedManagementApproach |
P137310
|
FINISHED |
| Object | systems engineering |
—
|
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: systems engineering | Statement: [NASA Apollo Program Office, usedManagementApproach, systems engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedManagementApproach Context triple: [NASA Apollo Program Office, usedManagementApproach, systems engineering]
-
A.
managementApproach
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
B.
usesManagementModel
chosen
Indicates that one entity applies, follows, or operates according to a particular management model in its management practices or structure.
-
C.
managementUse
Indicates that one entity uses or employs another entity specifically for management or administrative purposes.
-
D.
controlledApproachesTo
Indicates that one entity regulates or manages the methods or ways in which another entity can be approached.
-
E.
usedToApproach
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.