Triple
T20946472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debir |
E515855
|
entity |
| Predicate | modernIdentificationStatus |
P30421
|
FINISHED |
| Object | disputed |
—
|
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: disputed | Statement: [Debir, modernIdentificationStatus, disputed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernIdentificationStatus Context triple: [Debir, modernIdentificationStatus, disputed]
-
A.
modernIdentification
Indicates that one entity serves as the contemporary or currently accepted identification or classification of another entity.
-
B.
identityStatus
chosen
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
C.
identificationType
Indicates the specific kind or category of identification associated with an entity or relationship.
-
D.
hasNationalIdentity
Indicates that an entity possesses or is associated with a particular national identity or nationality.
-
E.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fad97aa48190b4be692e3afce8c9 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:56 p.m.