Triple
T33776437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Shuya |
E865535
|
entity |
| Predicate | titleHolderBelongsToHouse |
P62657
|
FINISHED |
| Object | House of Shuisky |
—
|
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: House of Shuisky | Statement: [Prince of Shuya, titleHolderBelongsToHouse, House of Shuisky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderBelongsToHouse Context triple: [Prince of Shuya, titleHolderBelongsToHouse, House of Shuisky]
-
A.
titleHolderBelongsTo
chosen
Indicates that the holder of a title is associated with or belongs to a particular entity, such as an organization, position, or domain.
-
B.
titleHolderHouse
Indicates that a particular house or noble family holds or is associated with a specific title.
-
C.
titleHolderCouldBe
Indicates that a particular entity is a possible or potential holder of a specified title or position.
-
D.
titleHolderHouseBranch
Indicates the specific branch of a house or family line that currently holds or is associated with a given title.
-
E.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
- 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_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 1, 2026, 1:45 a.m.