Triple
T35078585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clonbrock |
E1012370
|
entity |
| Predicate | hasNobleResident |
—
|
GENERATED |
| Object | Barons Clonbrock |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobleResident Context triple: [Clonbrock, hasNobleResident, Barons Clonbrock]
-
A.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
B.
hasNotableResident
chosen
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
hasNobleConnection
Indicates that one entity has a familial, social, or formal association with a member of the nobility or a noble lineage.
-
E.
hasTypicalResident
Indicates that an entity characteristically or commonly has a particular type of resident associated with it.
- F. None of above.
Provenance (1 batch)
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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.