Triple
T31480612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Alexander |
E803127
|
entity |
| Predicate | historicallyUsedByFamily |
P48489
|
FINISHED |
| Object | Alexander family |
—
|
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: Alexander family | Statement: [Viscount Alexander, historicallyUsedByFamily, Alexander family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyUsedByFamily Context triple: [Viscount Alexander, historicallyUsedByFamily, Alexander family]
-
A.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
usedByFamilyOf
Indicates that something is utilized or consumed by members of a particular family or household.
-
C.
formerlyUsedBy
chosen
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
-
D.
hasFamilyLegacy
Indicates that an entity possesses a heritage, tradition, or reputation passed down through its family across generations.
-
E.
usedByFamily
Indicates that something is regularly utilized or consumed by a family as a group.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
Created at: April 30, 2026, 9:32 p.m.