Triple
T1499555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Arc |
E29764
|
entity |
| Predicate | codenameTheme |
P25955
|
FINISHED |
| Object | magician classes |
—
|
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: magician classes | Statement: [Intel Arc, codenameTheme, magician classes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codenameTheme Context triple: [Intel Arc, codenameTheme, magician classes]
-
A.
codenameUser
Indicates that a user is assigned or associated with a particular codename.
-
B.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
endUseAsCodename
Indicates that an entity stops being used as a codename for another entity or concept.
-
D.
translationOfCodename
Indicates that one codename is a translated version of another codename, preserving its intended meaning across languages.
-
E.
securityCodename
Indicates that an entity is assigned a specific codename used for security, confidentiality, or protective identification purposes.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6f0ce988190aafab4a6e0dfd710 |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.