Triple
T18101600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noel family |
E433231
|
entity |
| Predicate | associatedCountyFamily |
P96913
|
FINISHED |
| Object | Rutland gentry |
—
|
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: Rutland gentry | Statement: [Noel family, associatedCountyFamily, Rutland gentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCountyFamily Context triple: [Noel family, associatedCountyFamily, Rutland gentry]
-
A.
associatedWithCounty
Indicates that an entity has a relationship or linkage to a specific county, such as jurisdiction, location, or administrative association.
-
B.
associatedCountyTitle
Indicates a relationship where a county is linked to or identified by a specific official title or designation.
-
C.
familyConnectionTo
Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
-
D.
hasParentCounty
Indicates that a given county is administratively or geographically contained within, and subordinate to, a specified parent county.
-
E.
familyAlliance
chosen
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb6fed8819090798683353a5c08 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.