Triple
T5246449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Force prison |
E118470
|
entity |
| Predicate | Petite ForceFunction |
P61697
|
FINISHED |
| Object | female prisoners |
—
|
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: female prisoners | Statement: [La Force prison, Petite ForceFunction, female prisoners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Petite ForceFunction Context triple: [La Force prison, Petite ForceFunction, female prisoners]
-
A.
isSmallForce
Indicates that the force involved has a relatively low magnitude compared to typical or relevant reference forces.
-
B.
describesForce
Indicates that one entity characterizes, explains, or specifies the nature or magnitude of a force acting on another entity or system.
-
C.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
D.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
E.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
- F. None of above. chosen
Provenance (4 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b5320748190bcf3be4b6c364f92 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd787975788190848ffbac87896efe |
completed | March 20, 2026, 4:40 p.m. |
Created at: March 20, 2026, 1:50 p.m.