Triple
T18832811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Viggo of Denmark |
E460576
|
entity |
| Predicate | socialStatusBeforeMarriage |
P47002
|
FINISHED |
| Object | dynastic prince |
—
|
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: dynastic prince | Statement: [Prince Viggo of Denmark, socialStatusBeforeMarriage, dynastic prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStatusBeforeMarriage Context triple: [Prince Viggo of Denmark, socialStatusBeforeMarriage, dynastic prince]
-
A.
socialStatusAfterMarriage
Indicates the social status an individual holds as a result of, or following, their marriage.
-
B.
marriageBefore
Indicates that one marriage event occurred earlier in time than another marriage event.
-
C.
spouseStatusAtMarriage
chosen
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
D.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
E.
partnerBeforeMarriage
Indicates that one entity was the romantic or life partner of another entity prior to their marriage.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99b540c8190a29e5f9d56791d41 |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.