Triple
T15218695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeacidae |
E363705
|
entity |
| Predicate | usedGenealogicalClaimFor |
P87598
|
FINISHED |
| Object | royal legitimacy |
—
|
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 legitimacy | Statement: [Aeacidae, usedGenealogicalClaimFor, royal legitimacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedGenealogicalClaimFor Context triple: [Aeacidae, usedGenealogicalClaimFor, royal legitimacy]
-
A.
historicalClaimBy
Indicates that a particular historical assertion or interpretation is attributed to a specific source or agent.
-
B.
historicalClaim
Indicates that an entity asserts or presents a statement about past events or conditions as a matter of historical fact.
-
C.
heritageClaimedBy
Indicates that a particular heritage, tradition, or cultural legacy is asserted or identified as belonging to a specific entity.
-
D.
hasGenealogicalInterest
Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage of another entity.
-
E.
usedToClaim
chosen
Indicates that something is employed as evidence, justification, or support in making a particular claim.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007709d3881908384f0fe1e0218d0 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.