Triple
T35422403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex |
E1023828
|
entity |
| Predicate | defeatRequirement |
P20842
|
FINISHED |
| Object | Two jumps |
—
|
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: Two jumps | Statement: [Rex, defeatRequirement, Two jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatRequirement Context triple: [Rex, defeatRequirement, Two jumps]
-
A.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
B.
conditionOfVictory
chosen
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
C.
defeatedThrough
Indicates that one entity achieved victory over another by means of a specified method, strategy, or intermediary factor.
-
D.
numberOfWinsRequired
Indicates the specific count of wins an entity must achieve to meet a defined goal, threshold, or condition.
-
E.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7958d59388190a937ac6f4c81d3c9 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.