Triple
T17099799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cramer family |
E414947
|
entity |
| Predicate | familyRivalryWith |
P41243
|
FINISHED |
| Object | Lord family |
—
|
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: Lord family | Statement: [Cramer family, familyRivalryWith, Lord family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRivalryWith Context triple: [Cramer family, familyRivalryWith, Lord family]
-
A.
siblingRival
Indicates a relationship where two siblings are in competition or conflict with each other.
-
B.
enemyFamily
chosen
Indicates that two entities belong to families that are hostile or in conflict with each other.
-
C.
interFamilyRelations
Indicates relationships or interactions that occur between different families or family units.
-
D.
notableFamilyConflict
Indicates a significant, recognized dispute or ongoing tension between members of the same family.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc00880481909cc0dbc169663a41 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.