Triple
T28940755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juana Maria |
E730441
|
entity |
| Predicate | timeInIsolation |
P167387
|
FINISHED |
| Object | approximately 18 years |
—
|
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: approximately 18 years | Statement: [Juana Maria, timeInIsolation, approximately 18 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInIsolation Context triple: [Juana Maria, timeInIsolation, approximately 18 years]
-
A.
hasIsolation
Indicates that an entity is separated or kept apart from others, typically to prevent interaction, influence, or contamination.
-
B.
isolatedBy
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
C.
isIsolated
Indicates that an entity exists or occurs separately from others, without direct contact, interaction, or connection.
-
D.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
E.
hasSeclusion
Indicates that one entity provides, involves, or is characterized by a state or condition of privacy, isolation, or separation from others for another entity.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 8:36 a.m.