Triple
T19987518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NES-101 |
E493971
|
entity |
| Predicate | bundledControllerModel |
P109341
|
FINISHED |
| Object | NES-039 |
—
|
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: NES-039 | Statement: [NES-101, bundledControllerModel, NES-039]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bundledControllerModel Context triple: [NES-101, bundledControllerModel, NES-039]
-
A.
bundledController
Indicates that one controller is packaged or grouped together with another controller as part of the same bundle or unit.
-
B.
renderingModel
Indicates the specific rendering engine or model used to generate the visual or graphical output for an entity.
-
C.
linkedModel
chosen
Indicates that one model is associated or connected to another model, typically to reference or reuse its structure or behavior.
-
D.
typicalControllerType
Indicates the usual or most common type of controller associated with, or used to operate, a given entity.
-
E.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
- F. None of above.
Provenance (3 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fdd1a5c8190af756632aac38bf4 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:29 p.m.