Triple
T11888340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henri II de Bourbon, Prince de Condé |
E282848
|
entity |
| Predicate | houseHeadUntil |
P102077
|
FINISHED |
| Object | 1646 |
—
|
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: 1646 | Statement: [Henri II de Bourbon, Prince de Condé, houseHeadUntil, 1646]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseHeadUntil Context triple: [Henri II de Bourbon, Prince de Condé, houseHeadUntil, 1646]
-
A.
house1
Indicates that something is identified or classified as a house or dwelling.
-
B.
chiefHouse
Indicates that a particular house serves as the primary or leading residence associated with a given entity (such as a person, group, or organization).
-
C.
houseFunction
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
D.
hasHeadhouse
Indicates that one structure (typically a station or facility) includes or is associated with a headhouse building that serves as its main entrance or service area.
-
E.
house2
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a2860c8190a21af5fcddbd2f1e |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.