Triple
T35690724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnin Konn system |
E1031280
|
entity |
| Predicate | hasPrimaryWorld |
P22156
|
FINISHED |
| Object | Burnin Konn |
E1031289
|
NE 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: Burnin Konn | Statement: [Burnin Konn system, hasPrimaryWorld, Burnin Konn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryWorld Context triple: [Burnin Konn system, hasPrimaryWorld, Burnin Konn]
-
A.
hasWorld
chosen
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
B.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasWorldNumber
Indicates that an entity is associated with a specific world identified by a particular number.
-
D.
hasPrimarySystem
Indicates that an entity is associated with or operates under a main or principal system among potentially multiple systems.
-
E.
hasPrimaryEnvironment
Indicates that an entity is associated with its main or most characteristic environment or setting.
- F. None of above.
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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38729104048190b20cdefbebc27fe0 |
completed | June 21, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.