Triple
T11544467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priest |
E273746
|
entity |
| Predicate | classWeakness |
P82039
|
FINISHED |
| Object | early-game tempo |
—
|
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: early-game tempo | Statement: [Priest, classWeakness, early-game tempo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classWeakness Context triple: [Priest, classWeakness, early-game tempo]
-
A.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
B.
playstyleWeakness
chosen
Indicates a relationship where one playstyle is particularly vulnerable or disadvantaged when facing another playstyle.
-
C.
weakenedDuring
Indicates that an entity’s strength, intensity, or effectiveness is reduced over the course of a specified time period or event.
-
D.
decayResistanceCause
Indicates that one factor or condition is the cause of another entity’s resistance to decay.
-
E.
causeOfWeakness
Indicates that one entity is the reason or source that brings about the weakness 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e1d754819089f3b6be3404fa0b |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.