Triple
T32041910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle DunBroch |
E818239
|
entity |
| Predicate | homeClan |
P73445
|
FINISHED |
| Object | Clan DunBroch |
—
|
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: Clan DunBroch | Statement: [Castle DunBroch, homeClan, Clan DunBroch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeClan Context triple: [Castle DunBroch, homeClan, Clan DunBroch]
-
A.
clanCentre
chosen
Indicates that one entity serves as the central location, headquarters, or main base for a particular clan or group.
-
B.
homeFaction
Indicates the faction or group to which an entity primarily belongs or is originally affiliated.
-
C.
homeClubRenamedFrom
Indicates that a sports club’s current home club identity was previously known under a different name.
-
D.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
E.
clanDistrict
Indicates that a clan is associated with, based in, or traditionally linked to a particular district.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:19 a.m.