Triple
T36005841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Meulan |
E1041268
|
entity |
| Predicate | nobilityHouse |
P182094
|
FINISHED |
| Object | House of Beaumont-Meulan |
—
|
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 Beaumont-Meulan | Statement: [County of Meulan, nobilityHouse, House of Beaumont-Meulan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobilityHouse Context triple: [County of Meulan, nobilityHouse, House of Beaumont-Meulan]
-
A.
noble house
chosen
Indicates a hierarchical familial or dynastic relationship in which individuals belong to a recognized aristocratic lineage or ruling family.
-
B.
nobleHouseType
Indicates the specific category or classification of a noble house (e.g., royal, ducal, baronial) within a hierarchy or system of nobility.
-
C.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
D.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
E.
notableNobleFaction
Indicates that a noble is significantly associated with or belongs to a particularly prominent or influential noble faction.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaffab08190abd3717d9fe857ba |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.