Triple
T36958669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Armor |
E914251
|
entity |
| Predicate | isLessPowerfulThan |
P24324
|
FINISHED |
| Object | Red Armor |
—
|
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: Red Armor | Statement: [Yellow Armor, isLessPowerfulThan, Red Armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLessPowerfulThan Context triple: [Yellow Armor, isLessPowerfulThan, Red Armor]
-
A.
weakerThan
chosen
Indicates that one entity has less strength, power, or effectiveness than another entity.
-
B.
isStrongerThan
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
-
C.
isPowerful
Indicates that an entity possesses great strength, influence, or capacity to affect outcomes relative to others.
-
D.
isEasierThan
Indicates that one entity requires less effort, difficulty, or complexity to accomplish, understand, or deal with than another entity.
-
E.
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.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.