Triple
T24812290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beylerbeyi of Rumelia |
E620821
|
entity |
| Predicate | rankComparedToOtherBeylerbeys |
P22893
|
FINISHED |
| Object | senior |
—
|
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: senior | Statement: [Beylerbeyi of Rumelia, rankComparedToOtherBeylerbeys, senior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankComparedToOtherBeylerbeys Context triple: [Beylerbeyi of Rumelia, rankComparedToOtherBeylerbeys, senior]
-
A.
hasPopulationRankInTurkey
Indicates the relative position of an entity in the ordered list of populations within Turkey, such as its rank by population size compared to other entities in the country.
-
B.
BayezidTitle
Indicates that a person holds or is associated with the title of Bayezid.
-
C.
rankComparedTo
chosen
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
D.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
-
E.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.