Triple
T22375801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozilla performance team |
E553148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software performance engineering team |
C8686
|
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: software performance engineering team Context triple: [Mozilla performance team, instanceOf, software performance engineering team]
-
A.
software development team
chosen
A software development team is a collaborative group of professionals with complementary technical and organizational skills who work together to design, build, test, and maintain software products or systems.
-
B.
software engineering organization
A software engineering organization is a structured group of people, processes, and tools dedicated to designing, building, testing, deploying, and maintaining software systems to meet specific business or user needs.
-
C.
performance group
A performance group is an organized ensemble of individuals who collaboratively present artistic or entertainment works to an audience, such as music, theater, dance, or other live or recorded performances.
-
D.
performance group
A performance group is an organized ensemble of individuals who collaboratively create and present artistic or entertainment works to an audience.
-
E.
software engineer
A software engineer is a professional who designs, develops, tests, and maintains software systems by applying principles of computer science and engineering to solve real-world problems.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.