Triple
T26782762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrope family |
E670292
|
entity |
| Predicate | notableEventInHistoryOfFamily |
P198077
|
FINISHED |
| Object | Scrope v Grosvenor heraldic dispute |
—
|
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: Scrope v Grosvenor heraldic dispute | Statement: [Scrope family, notableEventInHistoryOfFamily, Scrope v Grosvenor heraldic dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventInHistoryOfFamily Context triple: [Scrope family, notableEventInHistoryOfFamily, Scrope v Grosvenor heraldic dispute]
-
A.
notableFamilyActivity
Indicates that a family is particularly recognized for engaging in a specific activity or set of activities.
-
B.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
C.
historicalContextOfFamily
chosen
Indicates the broader historical circumstances, events, or conditions that form the background or setting for a particular family.
-
D.
hasSpouseNotableEvent
Indicates that a person’s spouse is associated with a notable event related to that person.
-
E.
historicalFamily
Indicates a familial relationship that existed between entities in the past, regardless of whether it still holds in the present.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: April 27, 2026, 4:10 a.m.