Triple
T15924319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosovo Protection Corps |
E386167
|
entity |
| Predicate | notRole |
P103705
|
FINISHED |
| Object | regular armed forces |
—
|
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: regular armed forces | Statement: [Kosovo Protection Corps, notRole, regular armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notRole Context triple: [Kosovo Protection Corps, notRole, regular armed forces]
-
A.
roleInNobody
Indicates that an entity has a specific role or function within the context of the work titled "Nobody" (e.g., a film, book, or other creative work named "Nobody").
-
B.
notStatus
chosen
Indicates that an entity does not have, is not in, or does not match a specified status or state.
-
C.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
D.
notAdministeredBy
Indicates that a particular treatment, medication, or intervention is explicitly not given or carried out by a specified agent or provider.
-
E.
notSubordinateTo
Indicates that one entity is not in a lower-ranking, subordinate, or reporting position to another entity within a hierarchy or organizational structure.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.