Triple
T27349775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maarva Andor |
E684322
|
entity |
| Predicate | adoptedChildFrom |
P100919
|
FINISHED |
| Object | Kenari |
—
|
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: Kenari | Statement: [Maarva Andor, adoptedChildFrom, Kenari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedChildFrom Context triple: [Maarva Andor, adoptedChildFrom, Kenari]
-
A.
adoptedChildrenFrom
chosen
Indicates a relationship where one entity has legally adopted children originating from another entity (such as a person, couple, or organization).
-
B.
adoptiveChild
Indicates that one entity is the child of another through legal adoption rather than biological descent.
-
C.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
D.
adoptedWith
Indicates that two or more entities were adopted at the same time or as part of the same adoption event or process.
-
E.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:47 a.m.