Triple
T36266463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victory Project simulation |
E892237
|
entity |
| Predicate | spouseOfMainProtagonistInSimulation |
P193421
|
FINISHED |
| Object | Jack Chambers |
—
|
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: Jack Chambers | Statement: [Victory Project simulation, spouseOfMainProtagonistInSimulation, Jack Chambers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfMainProtagonistInSimulation Context triple: [Victory Project simulation, spouseOfMainProtagonistInSimulation, Jack Chambers]
-
A.
spouseOfProtagonistOf
chosen
Indicates that one entity is the spouse (married partner) of the main character (protagonist) of another entity, typically a narrative work.
-
B.
spouseCharacterOf
Indicates a marital relationship where one character is the spouse of another character.
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spouseOfRole
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
-
E.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 3, 2026, 4:09 p.m.