Triple
T22375487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MZLA Technologies Corporation |
E553141
|
entity |
| Predicate | roleInThunderbird |
P147416
|
FINISHED |
| Object | development |
—
|
LITERAL FINISHED |
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: development | Statement: [MZLA Technologies Corporation, roleInThunderbird, development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInThunderbird Context triple: [MZLA Technologies Corporation, roleInThunderbird, development]
-
A.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
B.
memberOf
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
-
C.
siteRole
Indicates the specific function, responsibility, or position an entity holds within a particular site or location.
-
D.
roleInChickenfoot
Indicates that an entity participates in a game of Chickenfoot (a dominoes variant) in a specific role or capacity.
-
E.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
- F. None of above. chosen
Provenance (4 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15807cb748190abd9adc08ca1ad4f |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:45 p.m.