Triple
T19525963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batu Lintang, Sarawak |
E488518
|
entity |
| Predicate | campInmates |
P57303
|
FINISHED |
| Object | Allied military personnel |
—
|
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: Allied military personnel | Statement: [Batu Lintang, Sarawak, campInmates, Allied military personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campInmates Context triple: [Batu Lintang, Sarawak, campInmates, Allied military personnel]
-
A.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with another entity.
-
B.
hasPrisoners
chosen
Indicates that an entity holds or contains one or more individuals who are imprisoned or detained.
-
C.
securityForInmates
Indicates the provision or management of protective measures and safeguards specifically intended for inmates.
-
D.
majorPenitentiary
Indicates that an entity serves as a primary or principal penitentiary (major prison) within a given system or jurisdiction.
-
E.
estimatedPrisonerCount
Indicates the estimated number of prisoners associated with a particular context, such as a location, time period, or event.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363aeb8c8190be2bdd73e421af96 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.