Triple
T23647421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Greece |
E584075
|
entity |
| Predicate | secondDynastyHolder |
P153023
|
FINISHED |
| Object | George I of Greece |
—
|
NE NERFINISHED |
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: George I of Greece | Statement: [King of Greece, secondDynastyHolder, George I of Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondDynastyHolder Context triple: [King of Greece, secondDynastyHolder, George I of Greece]
-
A.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
B.
earlierDynasty
Indicates that one dynasty chronologically precedes another in historical succession.
-
C.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
-
D.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
E.
secondCreationMonarch
Indicates that an entity serves as the ruling monarch during the second creation or second foundational phase of a realm, order, or system.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28643348190add3666638951680 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:48 p.m.