Triple
T33775134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selwyn Tarth |
E865494
|
entity |
| Predicate | sendsToServe |
P177835
|
FINISHED |
| Object | Renly Baratheon |
—
|
NE NERFINISHED |
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: Renly Baratheon | Statement: [Selwyn Tarth, sendsToServe, Renly Baratheon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sendsToServe Context triple: [Selwyn Tarth, sendsToServe, Renly Baratheon]
-
A.
someServe
Indicates that one entity serves, assists, or performs duties for another entity in some capacity.
-
B.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
C.
wardServed
Indicates that a particular ward is provided with services or attended to by a specified entity (such as a person, organization, or facility).
-
D.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
E.
servesLineTo
Indicates that one entity provides or operates a particular service line or route for another entity or location.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:45 a.m.