Triple
T15551048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaqen H'ghar |
E370743
|
entity |
| Predicate | houseOfBlackAndWhiteStatus |
P81567
|
FINISHED |
| Object | servant of the Many-Faced God |
—
|
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: servant of the Many-Faced God | Statement: [Jaqen H'ghar, houseOfBlackAndWhiteStatus, servant of the Many-Faced God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseOfBlackAndWhiteStatus Context triple: [Jaqen H'ghar, houseOfBlackAndWhiteStatus, servant of the Many-Faced God]
-
A.
statusInHouse
chosen
Indicates the specific role, position, or standing an entity holds within a particular house or household.
-
B.
housePrefectStatus
Indicates the role or standing of an individual in relation to serving as a house prefect within an organization or institution.
-
C.
workBlackAndWhite
Indicates that the work is presented in black and white rather than in color.
-
D.
hasBlackFrontDoor
Indicates that one entity possesses or features a front door whose color is black.
-
E.
hasAllBlack
Indicates that the subject possesses or consists entirely of things that are black in color.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a9551288190a583e8291c35f521 |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:08 a.m.