Triple
T16739652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Lacy family |
E406802
|
entity |
| Predicate | dynastyDecline |
P59019
|
FINISHED |
| Object | late 13th century |
—
|
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: late 13th century | Statement: [de Lacy family, dynastyDecline, late 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyDecline Context triple: [de Lacy family, dynastyDecline, late 13th century]
-
A.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
B.
dynastyEndedWith
chosen
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
C.
dynastyAffected
Indicates that a particular dynasty is influenced, impacted, or changed in some way by another entity, event, or condition.
-
D.
dynastyInvolved
Indicates that a particular dynasty participates in, is associated with, or plays a role in the referenced event, process, or situation.
-
E.
extinctDynasty
Indicates that a dynasty has ceased to exist and no longer continues through ruling descendants or recognized lineage.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3d4fa48190b0db8f10a39d3ad8 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.