Triple
T29418800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Oldest Dragon |
E746099
|
entity |
| Predicate | comparativePower |
P2373
|
FINISHED |
| Object | more powerful than typical dragons |
—
|
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: more powerful than typical dragons | Statement: [the Oldest Dragon, comparativePower, more powerful than typical dragons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparativePower Context triple: [the Oldest Dragon, comparativePower, more powerful than typical dragons]
-
A.
isStrongerThan
chosen
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
-
B.
isPowerful
Indicates that an entity possesses great strength, influence, or capacity to affect outcomes relative to others.
-
C.
capitalCompared
Indicates a comparison between the capital cities associated with two entities, such as their relative status, attributes, or characteristics.
-
D.
combinesPowers
Indicates that two or more entities merge their abilities or strengths to produce a unified, often enhanced, effect.
-
E.
warPower
Indicates the authority, capability, or legal power to initiate, conduct, or manage acts of war or armed conflict.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 3:03 p.m.