Triple
T3254336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayyids |
E68259
|
entity |
| Predicate | lineageBasis |
P36142
|
FINISHED |
| Object | patrilineal descent |
—
|
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: patrilineal descent | Statement: [Sayyids, lineageBasis, patrilineal descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineageBasis Context triple: [Sayyids, lineageBasis, patrilineal descent]
-
A.
lineageClaim
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
B.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
C.
genealogicalLine
chosen
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
D.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
E.
namingBasis
Indicates that one entity serves as the reason, source, or criterion for how another entity is named or designated.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf65c9388190a0d74d6365ce631e |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.