Triple
T3044633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossbow |
E83414
|
entity |
| Predicate | hasDisadvantageComparedTo |
P7340
|
FINISHED |
| Object | longbow in rate of fire |
—
|
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: longbow in rate of fire | Statement: [Crossbow, hasDisadvantageComparedTo, longbow in rate of fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisadvantageComparedTo Context triple: [Crossbow, hasDisadvantageComparedTo, longbow in rate of fire]
-
A.
disadvantage
chosen
Indicates that one entity is in a less favorable, weaker, or hindered position relative to another in a given context.
-
B.
hasLessFinancialPowersThan
Indicates that one entity’s authority or capacity to make financial decisions or control financial resources is lower or more limited than that of another entity.
-
C.
opposedQualityTo
Indicates that one quality stands in direct opposition or contrast to another quality.
-
D.
weakerThan
Indicates that one entity has less strength, power, or effectiveness than another entity.
-
E.
hasTradeoff
Indicates that one option or outcome involves a compromise in which gaining certain benefits requires accepting corresponding costs or disadvantages.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b602ed881909a72662eb544866b |
completed | March 8, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.