Triple
T7495959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Hendrik of Mecklenburg-Schwerin |
E177128
|
entity |
| Predicate | endTimeAsConsort |
P77858
|
FINISHED |
| Object | 1934-07-03 |
—
|
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: 1934-07-03 | Statement: [Prince Hendrik of Mecklenburg-Schwerin, endTimeAsConsort, 1934-07-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeAsConsort Context triple: [Prince Hendrik of Mecklenburg-Schwerin, endTimeAsConsort, 1934-07-03]
-
A.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
B.
endTimeAsElectorPalatine
Indicates the point in time at which an entity’s role or tenure as Elector Palatine comes to an end.
-
C.
endTimeAsSuperiorGeneral
Indicates the point in time when an individual’s tenure or role as Superior General comes to an end.
-
D.
endTimeAsSecondLady
Indicates the point in time at which an individual’s tenure or role as the Second Lady concludes.
-
E.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:43 p.m.