Triple
T15425611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Frey |
E369500
|
entity |
| Predicate | risesTo |
P3787
|
FINISHED |
| Object | greater power after the War of the Five Kings |
—
|
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: greater power after the War of the Five Kings | Statement: [House Frey, risesTo, greater power after the War of the Five Kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: risesTo Context triple: [House Frey, risesTo, greater power after the War of the Five Kings]
-
A.
risesIn
Indicates that a river or similar watercourse originates or begins its flow in a specified location.
-
B.
endsUp
Indicates that one entity ultimately arrives at, becomes, or results in another state, condition, or location after some process or sequence of events.
-
C.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
D.
raisedTo
Indicates that one entity has been elevated, lifted, or brought up to a higher level, position, or state by another entity.
-
E.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec1fb288190a3625b8e4f487dd1 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.