Triple
T13140152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Carson |
E312189
|
entity |
| Predicate | householdRank |
P73827
|
FINISHED |
| Object | senior servant |
—
|
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: senior servant | Statement: [Mr. Carson, householdRank, senior servant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: householdRank Context triple: [Mr. Carson, householdRank, senior servant]
-
A.
rankWithinKazoku
Indicates the hierarchical position or status an individual holds within the Kazoku (Japanese peerage) nobility system.
-
B.
householdStatus
chosen
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
-
C.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
-
D.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
E.
patriarchRank
Indicates the hierarchical rank or level of authority held by a patriarch within a structured lineage or leadership system.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b84f1081908b9e2d54a64d4c2d |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:09 p.m.