Triple
T33775133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selwyn Tarth |
E865494
|
entity |
| Predicate | sendsIntoService |
P60783
|
FINISHED |
| Object | Brienne of Tarth |
—
|
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: Brienne of Tarth | Statement: [Selwyn Tarth, sendsIntoService, Brienne of Tarth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sendsIntoService Context triple: [Selwyn Tarth, sendsIntoService, Brienne of Tarth]
-
A.
takenIntoServiceAs
chosen
Indicates that one entity has been formally accepted, enrolled, or commissioned to perform service or duty for another entity.
-
B.
providesServiceTowards
Indicates that one entity delivers or performs a service directed to or for the benefit of another entity.
-
C.
publicServiceRemit
Indicates that an entity has an official obligation or mandate to provide services in the public interest, typically under a defined public-service framework or regulation.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
servedByServiceVia
Indicates that something receives service or is fulfilled through a specific service acting as the intermediary or delivery mechanism.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.