Triple
T35231389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherish |
E1017244
|
entity |
| Predicate | hasHouseArrestElement |
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: [Cherish, hasHouseArrestElement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHouseArrestElement Context triple: [Cherish, hasHouseArrestElement, 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.
hasPrison
Indicates that one entity possesses, contains, or is the location of a prison associated with another entity.
-
C.
hasBeenImprisonedBy
Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
-
D.
hasJail
Indicates that one entity possesses, operates, or is associated with a jail or detention facility.
-
E.
hasBeenImprisoned
Indicates that an entity has been confined or incarcerated in a prison or similar detention facility at some point in time.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:02 p.m.