Triple
T36827198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria (adopted surname) |
E910041
|
entity |
| Predicate | isAdoptedAs |
P186329
|
FINISHED |
| Object | chosen family name |
—
|
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: chosen family name | Statement: [Victoria (adopted surname), isAdoptedAs, chosen family name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdoptedAs Context triple: [Victoria (adopted surname), isAdoptedAs, chosen family name]
-
A.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
-
B.
hasBeenAdoptedIn
Indicates that something (such as a practice, policy, standard, or idea) has been formally accepted and put into use within a particular context, place, or organization.
-
C.
adoptedWith
Indicates that two or more entities were adopted at the same time or as part of the same adoption event or process.
-
D.
adoptadoEl
Indicates that one entity has been adopted by another entity (e.g., a person, family, or organization).
-
E.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabdd2d88190be1c8de7e499cb83 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7ca91f1808190b2a05c4b691da0bb |
completed | May 3, 2026, 10:22 p.m. |
Created at: May 3, 2026, 4:13 p.m.