Triple
T31578780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lepthoplosternum (disputed) |
E805765
|
entity |
| Predicate | familyPlacement |
P180984
|
FINISHED |
| Object | disputed |
—
|
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: disputed | Statement: [Lepthoplosternum (disputed), familyPlacement, disputed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyPlacement Context triple: [Lepthoplosternum (disputed), familyPlacement, disputed]
-
A.
fosterParents
Indicates a relationship where individuals act as temporary parental caregivers for a child who is not their biological or adopted offspring.
-
B.
adoptiveHome
Indicates that an entity serves as the adoptive home or placement setting for another entity, typically a child or animal, following an adoption process.
-
C.
adoptiveFamily
Indicates a familial relationship formed through legal adoption rather than biological descent.
-
D.
adoptiveParentsResidence
Indicates the place where the adoptive parents live or are legally resident.
-
E.
historicalFamilyPlacement
Indicates the recorded arrangement or position of an individual within a family structure at some point in the past.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 30, 2026, 10:22 p.m.