Triple
T6485981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nina Foch |
E146509
|
entity |
| Predicate | styleOfRole |
P59266
|
FINISHED |
| Object | poised characters |
—
|
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: poised characters | Statement: [Nina Foch, styleOfRole, poised characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfRole Context triple: [Nina Foch, styleOfRole, poised characters]
-
A.
roleCharacteristic
chosen
Indicates that a particular characteristic, quality, or attribute is associated with and helps define a given role or function.
-
B.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
stagePersonaOf
Indicates a relationship where one entity is the staged or performed persona, role, or character representation of another entity.
-
D.
styleDescribedAs
Indicates that the manner, aesthetic, or mode of something is characterized or labeled using a particular style description.
-
E.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a706d4c8190b7a3cc8855abcecb |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.