Triple
T6431901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بوستان |
E129796
|
entity |
| Predicate | مخاطب |
P16105
|
FINISHED |
| Object | عامه مردم |
—
|
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: عامه مردم | Statement: [بوستان, مخاطب, عامه مردم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: مخاطب Context triple: [بوستان, مخاطب, عامه مردم]
-
A.
addressedBy
chosen
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
B.
letterer
Indicates that one entity serves as the letterer of another, typically responsible for drawing or designing the lettering (such as text or captions) in that work.
-
C.
addresseeDescription
Indicates that one entity provides a descriptive characterization or identifying information about the addressee of a communication or message.
-
D.
correspondedWith
Indicates that two entities engaged in mutual communication, typically by exchanging messages or letters over a period of time.
-
E.
characterAddressed
Indicates that one character directs speech, communication, or attention specifically toward another character.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693cadf08190aca84888a3440b3d |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.