Triple
T15924324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosovo Protection Corps |
E386167
|
entity |
| Predicate | hasPersonnelOrigin |
P51517
|
FINISHED |
| Object | former Kosovo Liberation Army members |
—
|
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: former Kosovo Liberation Army members | Statement: [Kosovo Protection Corps, hasPersonnelOrigin, former Kosovo Liberation Army members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonnelOrigin Context triple: [Kosovo Protection Corps, hasPersonnelOrigin, former Kosovo Liberation Army members]
-
A.
personnelSource
chosen
Indicates the origin or provider from which personnel are obtained or assigned.
-
B.
committeeOfOrigin
Indicates the committee in which a proposal, bill, or item was first introduced or initially considered.
-
C.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
hasFormerStaffMember
Indicates that an entity once had a person as a staff member, but that person is no longer employed there.
-
E.
originPerson
Indicates that one person is the source, creator, or originating agent of another entity or action.
- 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.