Triple
T24196658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNTAC |
E599851
|
entity |
| Predicate | militaryPersonnelStrength |
P24266
|
FINISHED |
| Object | about 15000 |
—
|
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: about 15000 | Statement: [UNTAC, militaryPersonnelStrength, about 15000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryPersonnelStrength Context triple: [UNTAC, militaryPersonnelStrength, about 15000]
-
A.
personnelStrength
chosen
Indicates the number or capacity of people assigned to or available for a particular unit, organization, or operation.
-
B.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
C.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
D.
USForceStrength
Indicates the level or magnitude of military forces deployed or available by the United States in a given context.
-
E.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24ad83c819084ac9e34d2cc2120 |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.