Triple
T37364078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oiscingas |
E927660
|
entity |
| Predicate | hasRoyalHouseStyle |
P8992
|
FINISHED |
| Object | House of Oisc |
—
|
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 Oisc | Statement: [Oiscingas, hasRoyalHouseStyle, House of Oisc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalHouseStyle Context triple: [Oiscingas, hasRoyalHouseStyle, House of Oisc]
-
A.
hasDynasticHouseStyle
Indicates that an entity is associated with or characterized by a particular dynastic house’s stylistic tradition or aesthetic.
-
B.
hasRoyalHouse
chosen
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
C.
royalStyle
Indicates the formal manner or title by which a monarch or royal person is officially addressed or referred to.
-
D.
isMonarchicalStyle
Indicates that the relationship or action involves having or using a monarchical style, such as a royal or sovereign form of address or title.
-
E.
hasRoyalHousehold
Indicates that an entity possesses or is associated with a specific royal household as its official domestic or courtly establishment.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 3, 2026, 4:16 p.m.