Triple
T7390913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regine Olsen |
E170493
|
entity |
| Predicate | engagementStart |
P76316
|
FINISHED |
| Object | 1840 |
—
|
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: 1840 | Statement: [Regine Olsen, engagementStart, 1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementStart Context triple: [Regine Olsen, engagementStart, 1840]
-
A.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
B.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
C.
engagementPhase
Indicates the specific stage or phase an ongoing interaction, project, or relationship is currently in within its overall lifecycle.
-
D.
openingEngagementOf
Indicates that one event, action, or interaction serves as the initial or first engagement within a larger sequence, context, or relationship involving another entity or event.
-
E.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2216a5c8190a933b24fda4530d8 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0be2b1c8190bea06100a7caef2b |
completed | March 27, 2026, 9:03 p.m. |
Created at: March 27, 2026, 3:09 p.m.