Triple
T7662875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruth First |
E173549
|
entity |
| Predicate | detentionPeriod |
P69595
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Ruth First, detentionPeriod, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detentionPeriod Context triple: [Ruth First, detentionPeriod, 1963]
-
A.
detainedFor
Indicates that one entity is being held in custody or confinement because of, or as a consequence of, another entity (such as a reason, charge, or event).
-
B.
detainedUntil
Indicates that an entity is held in custody or confinement up to a specified time or until a particular condition is met.
-
C.
detentionType
Indicates the specific category or form of detention applied to an entity within a custodial or restrictive context.
-
D.
detainedAfter
Indicates that one entity is held in custody or confinement following another specified event or action.
-
E.
wasDetainedDuring
chosen
Indicates that an entity was held in custody or confinement for some period of time during a specified event or time interval.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 3:59 p.m.