Triple
T11839936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilus |
E281619
|
entity |
| Predicate | lineageStatus |
P4867
|
FINISHED |
| Object | royal ancestor |
—
|
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: royal ancestor | Statement: [Ilus, lineageStatus, royal ancestor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineageStatus Context triple: [Ilus, lineageStatus, royal ancestor]
-
A.
lineStatus
Indicates the current operational or functional state of a line or connection within a system.
-
B.
lineageClaim
chosen
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
C.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
-
D.
line8Status
Indicates the status or condition associated with the eighth line in a sequence, record, or structured data set.
-
E.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a63106b48190917817ec40d21a49 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.