Triple
T14664106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agworok |
E344318
|
entity |
| Predicate | hasMarriagePattern |
P11275
|
FINISHED |
| Object | exogamous between clans |
—
|
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: exogamous between clans | Statement: [Agworok, hasMarriagePattern, exogamous between clans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarriagePattern Context triple: [Agworok, hasMarriagePattern, exogamous between clans]
-
A.
marriagePattern
chosen
Indicates the typical form or structure of a marriage relationship, such as how partners are selected, organized, or related within a social or cultural system.
-
B.
hasMarriage
Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
-
C.
hasMaritalRelationshipType
Indicates the specific type or nature of the marital relationship that exists between two entities.
-
D.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
E.
hasMarriagePlot
Indicates that the work’s narrative centrally involves courtship, romantic relationships, or the progression toward marriage as a key plot element.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54ae5ac81908cc69891f280e5f7 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.