Triple
T33388778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DK0010272202 |
E854989
|
entity |
| Predicate | identifierStatus |
P178650
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [DK0010272202, identifierStatus, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifierStatus Context triple: [DK0010272202, identifierStatus, active]
-
A.
identityStatus
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
B.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
C.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
D.
identityStoredIn
Indicates that an entity’s identity information is kept or recorded within another entity or storage medium.
-
E.
identifierFor
Indicates that one entity serves as a unique identifying label or code for 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f713bfdc148190a249a7874320bab8 |
completed | May 3, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f7135fa2988190a20a94cfe616d754 |
completed | May 3, 2026, 9:20 a.m. |
Created at: May 1, 2026, 1:35 a.m.