Triple
T26719983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downey NASA industrial plant |
E673675
|
entity |
| Predicate | builtComponentOf |
P35910
|
FINISHED |
| Object | Apollo Command Module |
—
|
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: Apollo Command Module | Statement: [Downey NASA industrial plant, builtComponentOf, Apollo Command Module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtComponentOf Context triple: [Downey NASA industrial plant, builtComponentOf, Apollo Command Module]
-
A.
builtAsPartOf
chosen
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
-
B.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
C.
componentBuilt
Indicates that one entity has constructed, assembled, or otherwise created another entity as a component or part.
-
D.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
E.
builtThrough
Indicates that something was created, developed, or achieved by means of a specified method, process, or intermediary.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 3:40 a.m.