Triple
T26765603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ξ*− (dss) |
E674927
|
entity |
| Predicate | isSubjectToConfinement |
P1313
|
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: [Ξ*− (dss), isSubjectToConfinement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubjectToConfinement Context triple: [Ξ*− (dss), isSubjectToConfinement, true]
-
A.
isConfined
Indicates that an entity is restricted to a limited space or area, unable to move freely beyond defined boundaries.
-
B.
usesConfinementMethod
Indicates that one entity employs a particular method or technique to confine, restrain, or contain another entity or object.
-
C.
confinementMethod
Indicates the method or means by which an entity is confined, restrained, or kept in captivity.
-
D.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
E.
confinedFrom
Indicates that one entity is restricted, imprisoned, or kept within a place or condition as a result of another entity’s action or authority.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 3:59 a.m.