Triple
T35858445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azulai |
E1036572
|
entity |
| Predicate | isAssociatedWithLineage |
P152701
|
FINISHED |
| Object | Chida family |
—
|
NE NERFINISHED |
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: Chida family | Statement: [Azulai, isAssociatedWithLineage, Chida family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithLineage Context triple: [Azulai, isAssociatedWithLineage, Chida family]
-
A.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
B.
hasLineageMember
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
-
C.
hasLineageConnectionTo
chosen
Indicates a genealogical or ancestral relationship exists between two entities, such as descent, shared ancestry, or familial lineage.
-
D.
hasLineageCharacteristic
Indicates that an entity possesses a specific trait, feature, or quality that is inherited or derived from its lineage or ancestral line.
-
E.
hasLineageRole
Indicates a relationship where an entity holds a specific role or function within a lineage, ancestry, or genealogical chain.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.