Triple
T34368320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Foundling |
E882080
|
entity |
| Predicate | associatedWithNotableCharacter |
P64828
|
FINISHED |
| Object | Sophia Western |
E882454
|
NE 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: Sophia Western | Statement: [A Foundling, associatedWithNotableCharacter, Sophia Western]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNotableCharacter Context triple: [A Foundling, associatedWithNotableCharacter, Sophia Western]
-
A.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
B.
notableWorkCharacter
chosen
Indicates that a character appears in, is associated with, or plays a role in a particular notable work.
-
C.
notableSeriesCharacter
Indicates that an entity is a significant or well-known character appearing in a particular series.
-
D.
notableCharacterAffiliation
Indicates that a notable character is formally associated with, aligned to, or a member of a particular group, organization, or affiliation.
-
E.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
- F. None of above.
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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3718206f6c81908641e980f32e5c11 |
completed | June 20, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.