Triple
T15314288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macedonian phalanx |
E366114
|
entity |
| Predicate | hasTypicalEquipment |
P113532
|
FINISHED |
| Object | sarissa pike |
—
|
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: sarissa pike | Statement: [Macedonian phalanx, hasTypicalEquipment, sarissa pike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalEquipment Context triple: [Macedonian phalanx, hasTypicalEquipment, sarissa pike]
-
A.
hasSignatureEquipment
Indicates that an entity is associated with a distinctive or characteristic piece of equipment that is uniquely or notably linked to it.
-
B.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
C.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
D.
equipmentIncludes
chosen
Indicates that one entity contains, comprises, or has as part of its set of items a specified piece or set of equipment.
-
E.
hasTypicalArmor
Indicates that an entity normally wears or is equipped with a standard or characteristic type of armor.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd050108190a584543cb93943a4 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.