Triple
T1634034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X Development LLC |
E35323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and development subsidiary |
C425
|
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: research and development subsidiary Context triple: [X Development LLC, instanceOf, research and development subsidiary]
-
A.
research and development organization
chosen
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
-
B.
subsidiary brand
A subsidiary brand is a distinct brand owned and controlled by a parent company, operating under its own identity while leveraging the resources and strategic direction of the corporate owner.
-
C.
research facility
A research facility is a specialized institution equipped with laboratories, instruments, and resources where scientists and experts systematically investigate, experiment, and develop new knowledge or technologies.
-
D.
division of a national research institute
A division of a national research institute is a specialized organizational unit responsible for conducting and coordinating research, development, and related activities within a defined scientific or technical domain under the institute’s broader mission.
-
E.
public research institution
A public research institution is a government-funded organization dedicated to advancing knowledge and innovation through systematic investigation, experimentation, and dissemination of findings for the benefit of society.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.