Triple
T15859264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-35 Joint Program Office |
E384538
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multinational management organization |
C4089
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: multinational management organization Context triple: [F-35 Joint Program Office, instanceOf, multinational management organization]
-
A.
multinational consortium
A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
-
B.
international business organization
An international business organization is an entity that operates across national borders to coordinate, control, and manage commercial activities in multiple countries.
-
C.
multinational mission mechanism
chosen
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
-
D.
transnational organization
A transnational organization is an entity that operates across multiple countries, coordinating activities, resources, and decision-making beyond the authority or boundaries of any single nation-state.
-
E.
multinational retail corporation
A multinational retail corporation is a large company that operates chains of stores or online retail platforms in multiple countries, selling a wide range of consumer goods and services under a unified brand and management structure.
- F. None of above.
Provenance (1 batch)
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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.