Triple
T32795072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsha White |
E838737
|
entity |
| Predicate | hasNameInUniverse |
P197744
|
FINISHED |
| Object | Miss Marsha White |
—
|
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: Miss Marsha White | Statement: [Marsha White, hasNameInUniverse, Miss Marsha White]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInUniverse Context triple: [Marsha White, hasNameInUniverse, Miss Marsha White]
-
A.
inUniverseFamilyName
Indicates that an entity has a specific family surname within a particular fictional or narrative universe.
-
B.
namedAfterInUniverse
Indicates that one entity is, within the fictional or narrative universe, explicitly stated or implied to be named after another entity.
-
C.
universeName
Indicates the name or designated title assigned to a particular universe or cosmic setting.
-
D.
nameIsCommonIn
Indicates that a given name is frequently used or widely occurring within a specified group, region, or context.
-
E.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69fea5e75a5481908a04d91ee7255ebb |
completed | May 9, 2026, 3:11 a.m. |
Created at: May 1, 2026, 1:14 a.m.