Triple
T4761049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibzan |
E105697
|
entity |
| Predicate | broughtInWivesForSonsFrom |
P58372
|
FINISHED |
| Object | outside his clan |
—
|
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: outside his clan | Statement: [Ibzan, broughtInWivesForSonsFrom, outside his clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtInWivesForSonsFrom Context triple: [Ibzan, broughtInWivesForSonsFrom, outside his clan]
-
A.
sonInLaw
Indicates that one person is the husband of another person's child.
-
B.
connectedThroughMarriageVia
Indicates that two entities are related to each other by a marital connection that is mediated through one or more intermediate spouses or in-laws, rather than by a direct marriage between them.
-
C.
marriedInto
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
D.
houseByMarriage
Indicates a familial or household relationship established through marriage rather than by blood or direct residence.
-
E.
spouseDynasty
Indicates that there is a marital relationship linking an entity to the dynasty (family line or ruling house) of their spouse.
- F. None of above. chosen
Provenance (4 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.