Triple
T29351508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | celere division |
E744325
|
entity |
| Predicate | includesArm |
P200941
|
FINISHED |
| Object | cavalry |
—
|
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: cavalry | Statement: [celere division, includesArm, cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesArm Context triple: [celere division, includesArm, cavalry]
-
A.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
B.
hasArmWidth
Indicates that one entity has a specified measurement for the width of its arm.
-
C.
armsIncorporatedIn
Indicates that one entity’s arms or armorial bearings are formally included within, or combined into, the heraldic arms of another entity.
-
D.
armamentIncludes
Indicates that a larger weapon system, vehicle, or platform has a specified weapon or piece of equipment as part of its armament.
-
E.
isARMBased
Indicates that something is based on or built using the ARM processor architecture.
- F. None of above. chosen
Provenance (4 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
| PDg | Predicate description generation | batch_69ffbb1b3b888190ba329ad321fc3f3d |
completed | May 9, 2026, 10:54 p.m. |
Created at: April 28, 2026, 2:06 p.m.