Triple
T31142877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Upper Ossory |
E793836
|
entity |
| Predicate | titleRankOrder |
P58612
|
FINISHED |
| Object | below 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: below viscount | Statement: [Baron Upper Ossory, titleRankOrder, below viscount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleRankOrder Context triple: [Baron Upper Ossory, titleRankOrder, below viscount]
-
A.
organRank
Indicates a hierarchical or priority ordering among organs relative to one another.
-
B.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
C.
rankExample
Indicates that one entity is used as an example or instance to illustrate the rank or ordering of another entity.
-
D.
canonicalRank
chosen
Indicates the standard or officially recognized rank or level assigned to an entity within an ordered hierarchy.
-
E.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 29, 2026, 9:06 p.m.