Triple
T14595348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oultremont family |
E342546
|
entity |
| Predicate | hasTitleTradition |
P11127
|
FINISHED |
| Object | count |
—
|
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: count | Statement: [Oultremont family, hasTitleTradition, count]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleTradition Context triple: [Oultremont family, hasTitleTradition, count]
-
A.
usesTraditionalTitleSystem
Indicates that an entity follows or applies a customary, historically established system of formal titles or honorifics in its social or organizational structure.
-
B.
traditionalTitle
chosen
Indicates that an entity holds or is associated with a customary or historically established title or honorific within a cultural or social tradition.
-
C.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
-
D.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
E.
mainTradition
Indicates that one entity represents the primary or dominant tradition 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43581348190b5362251c3a89654 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.