Triple
T21415576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unique Forms of Continuity in Space |
E528291
|
entity |
| Predicate | castInBronze |
P143882
|
FINISHED |
| Object | posthumously |
—
|
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: posthumously | Statement: [Unique Forms of Continuity in Space, castInBronze, posthumously]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castInBronze Context triple: [Unique Forms of Continuity in Space, castInBronze, posthumously]
-
A.
castIn
Indicates that an actor or performer appears in a particular film, show, or production.
-
B.
castBy
Indicates that one entity (typically a role or character) is portrayed or performed by another entity (typically an actor or performer).
-
C.
castType
Indicates the specific kind or category of casting relationship that exists between two entities.
-
D.
castingChoiceFor
Indicates a relationship where a particular casting decision or option is selected or designated for a specific role, production, or performance.
-
E.
cast
Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b204dcf08190b24c35746ca467d0 |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:45 p.m.