Triple
T20191648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucina |
E492990
|
entity |
| Predicate | parentDetermination |
P139072
|
FINISHED |
| Object | mother determined by Chrom’s marriage |
—
|
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: mother determined by Chrom’s marriage | Statement: [Lucina, parentDetermination, mother determined by Chrom’s marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentDetermination Context triple: [Lucina, parentDetermination, mother determined by Chrom’s marriage]
-
A.
parentService
Indicates that one service functions as the higher-level or owning service in relation to another, which depends on or is derived from it.
-
B.
parent
Indicates a relationship where one entity is the direct mother or father of another entity, from whom that other entity is descended.
-
C.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
D.
parentCourt
Indicates that one court is hierarchically above and has authority over another court within a judicial system.
-
E.
parentageIncludes
Indicates that a given parentage or lineage set contains or encompasses a particular parent or ancestral relationship.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad593f88190a1e534fed38b3cd7 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:37 p.m.