Triple
T22615736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | beylerbey |
E558139
|
entity |
| Predicate | wasAddressedAs |
P148938
|
FINISHED |
| Object | pasha in many cases |
—
|
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: pasha in many cases | Statement: [beylerbey, wasAddressedAs, pasha in many cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAddressedAs Context triple: [beylerbey, wasAddressedAs, pasha in many cases]
-
A.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
B.
addressedFor
Indicates that something is directed, designated, or intended for a particular recipient or target.
-
C.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
-
D.
addressedBefore
Indicates that one entity was addressed or spoken to prior to another entity in time.
-
E.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
- F. None of above. chosen
Provenance (4 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167edec2481909c2f06607b3cb8f6 |
completed | April 29, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 2:59 p.m.