Triple
T23408590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaitian |
E560001
|
entity |
| Predicate | wasUnderHouseArrest |
P33293
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zaitian, wasUnderHouseArrest, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUnderHouseArrest Context triple: [Zaitian, wasUnderHouseArrest, true]
-
A.
placedUnderHouseArrest
chosen
Indicates that an authority has confined an entity to a specified residence, restricting their freedom of movement as a form of legal or disciplinary control.
-
B.
hasBeenImprisonedBy
Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
-
C.
hasBeenImprisoned
Indicates that an entity has been confined or incarcerated in a prison or similar detention facility at some point in time.
-
D.
wasDetainedDuring
Indicates that an entity was held in custody or confinement for some period of time during a specified event or time interval.
-
E.
wasImprisonedIn
Indicates that an entity was held in confinement or incarcerated at a particular place or facility.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50fff10819094e71fb0c11b7d95 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.