Triple
T2472788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xerox PARC |
E55015
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer science research laboratory |
C9196
|
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: computer science research laboratory Context triple: [Xerox PARC, instanceOf, computer science research laboratory]
-
A.
research center program
A research center program is an organized initiative within a research institution that coordinates projects, resources, and collaborations to advance inquiry and innovation in a specific field or set of related disciplines.
-
B.
human–computer interaction research center
A human–computer interaction research center is an interdisciplinary organization that studies, designs, and evaluates interactive technologies to improve how people use and experience computer systems.
-
C.
computer science school
A computer science school is an educational institution or program dedicated to teaching the principles, theories, and practical skills of computing, programming, and information technology.
-
D.
private laboratory
chosen
A private laboratory is a non-public scientific facility, typically owned by a company or individual, where controlled experiments, analyses, and research are conducted for proprietary, commercial, or specialized purposes.
-
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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:45 p.m.