Triple
T18552651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barão (Portugal) |
E453414
|
entity |
| Predicate | relativeRankInEurope |
P84197
|
FINISHED |
| Object | one of the lowest hereditary noble ranks |
—
|
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: one of the lowest hereditary noble ranks | Statement: [Barão (Portugal), relativeRankInEurope, one of the lowest hereditary noble ranks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeRankInEurope Context triple: [Barão (Portugal), relativeRankInEurope, one of the lowest hereditary noble ranks]
-
A.
rankingInEurope
chosen
Indicates the position or level an entity holds within a comparative ranking limited to Europe.
-
B.
areaRankingInEurope
Indicates the position of an entity in a size-based ranking of areas within Europe.
-
C.
rankingInCountry
Indicates the position or level an entity holds within an ordered list specific to a particular country.
-
D.
rankByLengthInEurope
Indicates that entities are ordered or compared based on their length specifically within the context of Europe.
-
E.
rankInCountry
Indicates the position or standing of an entity within a specific country according to some ranking or ordered criterion.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538027b94819082a4c4af66e170d7 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.