Triple
T22539351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naunet |
E557242
|
entity |
| Predicate | abstractDomain |
P148588
|
FINISHED |
| Object | primordial chaos |
—
|
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: primordial chaos | Statement: [Naunet, abstractDomain, primordial chaos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abstractDomain Context triple: [Naunet, abstractDomain, primordial chaos]
-
A.
assumptionOnDomain
Indicates that a particular assumption or constraint is specified to hold over a given domain or set of entities.
-
B.
notationDomain
Indicates a relationship where a notation system is associated with, or defined over, a particular domain in which it is valid or applicable.
-
C.
publicDomain
Indicates that a work or resource is not protected by intellectual property rights and is freely available for anyone to use, copy, modify, and distribute without restriction.
-
D.
affectedDomain
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
E.
partOfDomain
Indicates that one entity belongs to, is included within, or is a constituent part of the scope or domain defined by another entity.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f302cd4819098c97ca4fa96363e |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.