Triple
T19797363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Lennox |
E475577
|
entity |
| Predicate | undergoesArc |
P137364
|
FINISHED |
| Object | from isolation to connection |
—
|
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: from isolation to connection | Statement: [Mary Lennox, undergoesArc, from isolation to connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergoesArc Context triple: [Mary Lennox, undergoesArc, from isolation to connection]
-
A.
undergoing
Indicates that an entity is currently experiencing, being subjected to, or in the process of a particular action, change, or treatment.
-
B.
formsArcOf
Indicates that one entity curves around or spans between points so as to create an arc in relation to another entity.
-
C.
hasArc
Indicates that there is a directed connection or edge from one entity to another, often representing a link in a graph or network.
-
D.
arc
Indicates a directed relationship from one entity to another, often representing a one-way connection or transition between them.
-
E.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c877288190b56ee7eedea710a3 |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.