Triple
T31100335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortals |
E792655
|
entity |
| Predicate | unitStrength |
P24266
|
FINISHED |
| Object | 10000 soldiers |
—
|
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: 10000 soldiers | Statement: [Immortals, unitStrength, 10000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitStrength Context triple: [Immortals, unitStrength, 10000 soldiers]
-
A.
UNForcesStrength
Indicates the size or level of military capability of United Nations forces involved in a given context.
-
B.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
C.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
D.
commandingForce1Strength
Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
-
E.
personnelStrength
chosen
Indicates the number or capacity of people assigned to or available for a particular unit, organization, or operation.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.