Triple
T11128587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese peerage |
E263212
|
entity |
| Predicate | fourthRank |
P18793
|
FINISHED |
| Object | viscount |
—
|
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: viscount | Statement: [Portuguese peerage, fourthRank, viscount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthRank Context triple: [Portuguese peerage, fourthRank, viscount]
-
A.
fourthPlace
Indicates that an entity holds the fourth position or rank in an ordered sequence, competition, or hierarchy.
-
B.
fourthTier
chosen
Indicates that one entity occupies the fourth level, rank, or tier in a hierarchical ordering or classification relative to others.
-
C.
fourthSingle
Indicates that an entity is the fourth individual item or occurrence in a sequence, considered on its own rather than as part of a group.
-
D.
fourthLevelRepresents
Indicates that one entity serves as a fourth-level representation or abstraction of another within a hierarchical structure.
-
E.
thirdRankSee
Indicates that an entity occupying a third rank or position observes, notices, or visually perceives 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e830e804819097fcc3826d84dab8 |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.