Triple
T26408704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noekeon |
E663898
|
entity |
| Predicate | statusInNESSIE |
P179778
|
FINISHED |
| Object | not selected as final NESSIE primitive |
—
|
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: not selected as final NESSIE primitive | Statement: [Noekeon, statusInNESSIE, not selected as final NESSIE primitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInNESSIE Context triple: [Noekeon, statusInNESSIE, not selected as final NESSIE primitive]
-
A.
statusInDatabases
Indicates the current state or condition an entity has within one or more database systems.
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
D.
statisticsStatus
Indicates the current state or condition of statistical data or statistical processing for an entity.
-
E.
statusInDoctrine
Indicates the recognized standing or role that something holds within a particular doctrinal or theological system.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: April 26, 2026, 11:36 p.m.