Triple
T36664482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian-occupied Ljubljana Province |
E905217
|
entity |
| Predicate | hasOccupationForce |
P14275
|
FINISHED |
| Object | Royal Italian Army |
—
|
NE NERFINISHED |
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: Royal Italian Army | Statement: [Italian-occupied Ljubljana Province, hasOccupationForce, Royal Italian Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupationForce Context triple: [Italian-occupied Ljubljana Province, hasOccupationForce, Royal Italian Army]
-
A.
hasReserveForces
Indicates that an entity possesses additional military or security personnel kept in reserve for potential future deployment or use.
-
B.
occupationForcesCommandedBy
Indicates that a particular occupation force is under the command or authority of a specified commander or commanding entity.
-
C.
hasCivilianWorkforce
Indicates that an entity employs or is associated with a group of civilian (non-military) workers.
-
D.
hasMilitaryPresence
chosen
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
E.
hasArmedForces
Indicates that an entity possesses or maintains organized military forces under its control.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c77ef4108190aa83a9f595e34905 |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.