Triple
T29229876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SunView |
E741036
|
entity |
| Predicate | developerInstanceOf |
P179040
|
FINISHED |
| Object | Sun Microsystems is a technology company |
—
|
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: Sun Microsystems is a technology company | Statement: [SunView, developerInstanceOf, Sun Microsystems is a technology company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerInstanceOf Context triple: [SunView, developerInstanceOf, Sun Microsystems is a technology company]
-
A.
sonInstanceOf
Indicates that an entity is a specific instance or example of the general concept or class represented by "son."
-
B.
instanceOf
relation of type constraints
-
C.
possibleInstanceOf
Indicates that an entity may be an instance of a given class or type, but this classification is uncertain or not definitively established.
-
D.
autoreInstanceOf
Indicates that one entity is an automatically generated or system-created instance of another entity or class.
-
E.
composerInstanceOf
Indicates that a composer belongs to or is classified as a specific type, category, or class of composers.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 28, 2026, 12:18 p.m.