Triple
T25507779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Britomart |
E639290
|
entity |
| Predicate | seesFutureLineageIn |
P158610
|
FINISHED |
| Object | enchanted mirror |
—
|
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: enchanted mirror | Statement: [Britomart, seesFutureLineageIn, enchanted mirror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seesFutureLineageIn Context triple: [Britomart, seesFutureLineageIn, enchanted mirror]
-
A.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
B.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
C.
successorInLineage
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
D.
hasLineageConnectionTo
Indicates a genealogical or ancestral relationship exists between two entities, such as descent, shared ancestry, or familial lineage.
-
E.
hasLeaderLineage
Indicates that an entity’s lineage or ancestry includes one or more individuals who have held a leadership role.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80749f88190a5c2a70e7370003b |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:47 p.m.