Triple
T27561999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samana |
E695793
|
entity |
| Predicate | lineageAssociation |
P124948
|
FINISHED |
| Object | HouseholdOfTheImams |
—
|
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: HouseholdOfTheImams | Statement: [Samana, lineageAssociation, HouseholdOfTheImams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineageAssociation Context triple: [Samana, lineageAssociation, HouseholdOfTheImams]
-
A.
lineageRelatedTo
chosen
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
B.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
C.
lineageSystem
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
D.
lineageConcept
Indicates a conceptual or abstract relationship of lineage, such as ancestry or descent, between entities.
-
E.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 1:39 p.m.