Triple
T17602543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soubise |
E428738
|
entity |
| Predicate | relatedEstate |
P19033
|
FINISHED |
| Object | Rohan estates in Brittany |
—
|
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: Rohan estates in Brittany | Statement: [Soubise, relatedEstate, Rohan estates in Brittany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEstate Context triple: [Soubise, relatedEstate, Rohan estates in Brittany]
-
A.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
B.
nearbyEstate
Indicates that one estate is located close to another estate in physical space.
-
C.
realEstate
Indicates a relationship where an entity owns, manages, or is otherwise associated with real property such as land or buildings.
-
D.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
-
E.
hasAssociatedEstate
chosen
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c49dbe081909bd39879c70fe27c |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b500c924819087c7107f86970675 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.