Triple
T19009299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Greece and Denmark |
E465175
|
entity |
| Predicate | statusInGreece |
P130447
|
FINISHED |
| Object | member of former Greek royal house |
—
|
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: member of former Greek royal house | Statement: [Prince of Greece and Denmark, statusInGreece, member of former Greek royal house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInGreece Context triple: [Prince of Greece and Denmark, statusInGreece, member of former Greek royal house]
-
A.
legalStatusForGreece
chosen
Indicates the legal status or standing of something specifically within the jurisdiction of Greece.
-
B.
significanceForGreece
Indicates that something holds particular importance, impact, or relevance specifically in the context of Greece.
-
C.
rankByAreaInGreece
Indicates the relative ordering of entities based on their area size within the geographic boundaries of Greece.
-
D.
statusInTurkey
Indicates the legal, social, or official condition or standing that an entity holds within the context of Turkey.
-
E.
statusInGhana
Indicates the legal, social, or official standing or condition an entity holds within the context of Ghana.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a72aa88190a04f13cd14ee77d4 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.