Triple
T33402001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Phoenix |
E855324
|
entity |
| Predicate | usesBirthName |
P18679
|
FINISHED |
| Object | Summer Joy Bottom |
—
|
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: Summer Joy Bottom | Statement: [Summer Phoenix, usesBirthName, Summer Joy Bottom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBirthName Context triple: [Summer Phoenix, usesBirthName, Summer Joy Bottom]
-
A.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by another entity.
-
B.
appliesToPersonBirthName
chosen
Indicates that the referenced value is used as the birth name of the specified person.
-
C.
usedAsBirthSurnameOf
Indicates that a particular surname served as the family name an individual was born with.
-
D.
usesNameForm
Indicates that one entity adopts or applies a particular standardized form or variant of a name associated with another entity.
-
E.
usesPersonalNamesFrom
Indicates that one entity employs or adopts the system or set of personal names originating from 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:36 a.m.