Triple
T38240777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hand of the King (Bran I) |
E1013753
|
entity |
| Predicate | servesAsChiefAdvisorTo |
P4479
|
FINISHED |
| Object | Bran I of House Stark |
—
|
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: Bran I of House Stark | Statement: [Hand of the King (Bran I), servesAsChiefAdvisorTo, Bran I of House Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsChiefAdvisorTo Context triple: [Hand of the King (Bran I), servesAsChiefAdvisorTo, Bran I of House Stark]
-
A.
advisorOf
Indicates that one entity serves as an advisor, providing guidance or counsel, to another entity.
-
B.
notableAdvisor
Indicates that one entity serves, or has served, as a significant or distinguished advisor to another entity.
-
C.
advisoryCouncilChairedBy
Indicates that an advisory council is led or presided over by a specified chairperson or chairing entity.
-
D.
isPrincipalAdvisorTo
chosen
Indicates that one entity serves as the main or primary advisor to another entity, providing overarching guidance or counsel.
-
E.
hasChiefInvestmentOfficer
Indicates that an entity has a specific person or role serving as its Chief Investment Officer.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.