Triple
T27957559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fu Hao |
E703591
|
entity |
| Predicate | commandedForcesSize |
P130574
|
FINISHED |
| Object | thousands of 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: thousands of soldiers | Statement: [Fu Hao, commandedForcesSize, thousands of soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedForcesSize Context triple: [Fu Hao, commandedForcesSize, thousands of soldiers]
-
A.
commandingForceSize
chosen
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
B.
commandedForcesOf
Indicates that one entity held command authority over the military or armed forces associated with another entity.
-
C.
commandedTroopsAt
Indicates that a person held command authority over military forces at a specific location or during a particular operation.
-
D.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
E.
numberOfUnitsCommanded
Indicates the quantity of units that an entity is in command of within a given context.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 7:29 p.m.