Triple
T35118714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poor Fellows |
E1014110
|
entity |
| Predicate | statusDuringTargaryenConquest |
P200249
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [Poor Fellows, statusDuringTargaryenConquest, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringTargaryenConquest Context triple: [Poor Fellows, statusDuringTargaryenConquest, active]
-
A.
activityDuringWarOfFiveKings
Indicates that an entity was involved in or undertook some activity during the period of the War of the Five Kings.
-
B.
methodOfGainingCasterlyRock
Indicates the manner or process by which an entity comes to possess or control Casterly Rock.
-
C.
headDuringWarOfFiveKings
Indicates that an entity served as the head or leader of another entity during the period of the War of the Five Kings.
-
D.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
E.
unitesThronesOf
Indicates a relationship in which one entity brings together and consolidates the separate thrones or rulerships of other entities into a single unified authority.
- F. None of above. chosen
Provenance (4 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69ff7c96036c8190bfae5ec9b5a1965f |
completed | May 9, 2026, 6:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.