Triple
T11128541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | da Gama family |
E263211
|
entity |
| Predicate | patrilinealDescent |
P41041
|
FINISHED |
| Object | Gama lineage |
—
|
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: Gama lineage | Statement: [da Gama family, patrilinealDescent, Gama lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patrilinealDescent Context triple: [da Gama family, patrilinealDescent, Gama lineage]
-
A.
patriarchalLineage
chosen
Indicates a familial relationship where descent, inheritance, or identity is traced through the male line or father’s ancestry.
-
B.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
C.
ofDescent
Indicates a genealogical or ancestral relationship, specifying that one entity descends from or originates from another.
-
D.
clanInheritance
Indicates that rights, titles, or property are passed down within a clan according to its internal rules of succession.
-
E.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e830e804819097fcc3826d84dab8 |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.