Triple
T27487267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip of Valois |
E693771
|
entity |
| Predicate | heldTitleBeforeKingship |
P159695
|
FINISHED |
| Object | Count of Alençon |
—
|
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: Count of Alençon | Statement: [Philip of Valois, heldTitleBeforeKingship, Count of Alençon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTitleBeforeKingship Context triple: [Philip of Valois, heldTitleBeforeKingship, Count of Alençon]
-
A.
titleHeldBeforeSuccession
chosen
Indicates that an entity held a specific title or position prior to a particular succession event.
-
B.
heldTitleFrom
Indicates that an entity possessed or held a particular title starting from a specified point in time.
-
C.
associatedTitleAfterEnthronement
Indicates the formal title or designation that is linked to an individual specifically after they have been enthroned or installed in an official position.
-
D.
sovereignTitleUntil
Indicates that an entity held a particular sovereign title or rulership status continuously up to a specified end date or point in time.
-
E.
roleInKingship
Indicates that an entity holds or plays a specific role or position within a system of kingship or royal authority.
- 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_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 1:03 p.m.