Triple
T18456032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Başpehlivan |
E450904
|
entity |
| Predicate | hasSubordinateRank |
P67578
|
FINISHED |
| Object | başaltı (runner‑up division) |
—
|
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: başaltı (runner‑up division) | Statement: [Başpehlivan, hasSubordinateRank, başaltı (runner‑up division)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubordinateRank Context triple: [Başpehlivan, hasSubordinateRank, başaltı (runner‑up division)]
-
A.
hasSubranking
chosen
Indicates that one ranking is a subordinate or nested ranking within another ranking.
-
B.
notSubordinateTo
Indicates that one entity is not in a lower-ranking, subordinate, or reporting position to another entity within a hierarchy or organizational structure.
-
C.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
D.
hasSubordinateFunction
Indicates that one function operates under the authority, control, or scope of another function as its subordinate.
-
E.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264c10408190b2085ade88655c7d |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.