Triple
T24812308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beylerbeyi of Rumelia |
E620821
|
entity |
| Predicate | equivalentRoleType |
P7006
|
FINISHED |
| Object | provincial governor-general |
—
|
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: provincial governor-general | Statement: [Beylerbeyi of Rumelia, equivalentRoleType, provincial governor-general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentRoleType Context triple: [Beylerbeyi of Rumelia, equivalentRoleType, provincial governor-general]
-
A.
hasEquivalentRole
chosen
Indicates that two entities hold roles that are functionally the same or interchangeable in a given context.
-
B.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
C.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
E.
roleSimilarTo
Indicates that two entities have roles or functions that are alike or closely comparable in nature or responsibility.
- 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:50 a.m.