Triple
T27487254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip of Valois |
E693771
|
entity |
| Predicate | wasFirstKingFromHouse |
P3535
|
FINISHED |
| Object | House of Valois |
—
|
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: House of Valois | Statement: [Philip of Valois, wasFirstKingFromHouse, House of Valois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstKingFromHouse Context triple: [Philip of Valois, wasFirstKingFromHouse, House of Valois]
-
A.
firstMonarch
chosen
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
B.
royalHouseFounder
Indicates that one entity is the person who founded or established the royal house or dynasty to which the other entity belongs.
-
C.
firstMonarchOfCurrentDynastyReignStart
Indicates the date or time when the reign of the first monarch of the current ruling dynasty began.
-
D.
firstKnownLord
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
-
E.
wasKingDuring
Indicates that one entity held the position or title of king throughout the time period associated with another entity.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e86625081909d5cc4b5fc1bd3d5 |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:03 p.m.