Triple
T37155230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amy Ryan |
E920476
|
entity |
| Predicate | laterUsedSurname |
P175346
|
FINISHED |
| Object | Ryan |
—
|
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: Ryan | Statement: [Amy Ryan, laterUsedSurname, Ryan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUsedSurname Context triple: [Amy Ryan, laterUsedSurname, Ryan]
-
A.
usedSurnameFor
Indicates that one entity adopted or employed another entity’s surname as the name by which they were known or referred to.
-
B.
usedAsSurname
Indicates that something functions as a family name borne by a person or group of people.
-
C.
surnameUsedIn
Indicates that a particular surname is used or borne within a specified context, such as by a person, family, or group.
-
D.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
-
E.
familyNameUsed
chosen
Indicates that one entity uses or is identified by the family name (surname) associated with another entity.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00d08e8fac8190b59359134e6e1c03 |
completed | May 10, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_6a00d0127c088190a6f5b360450af113 |
completed | May 10, 2026, 6:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.