Triple
T3254364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayyids |
E68259
|
entity |
| Predicate | genealogicalDocumentation |
P46883
|
FINISHED |
| Object | often maintain family trees |
—
|
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: often maintain family trees | Statement: [Sayyids, genealogicalDocumentation, often maintain family trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genealogicalDocumentation Context triple: [Sayyids, genealogicalDocumentation, often maintain family trees]
-
A.
genealogicalFunction
Indicates a genealogical relationship or role that one entity holds in relation to another within a family or ancestry structure.
-
B.
genealogicalDescription
Indicates a textual description that explains the genealogical relationships or lineage connections among entities.
-
C.
hasGenealogicalInterest
Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage of another entity.
-
D.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
E.
genealogicalStatus
Indicates the familial or ancestral relationship that one individual has to another within a genealogy.
- 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_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. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.