Triple
T11652969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سربراہِ مملکت |
E276951
|
entity |
| Predicate | foundInSystem |
P33705
|
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: [سربراہِ مملکت, foundInSystem, جمہوری نظام]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInSystem Context triple: [سربراہِ مملکت, foundInSystem, جمہوری نظام]
-
A.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
-
B.
foundInStructure
Indicates that an entity is located within, contained by, or structurally part of another entity or structure.
-
C.
locationInSystem
chosen
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
D.
foundInRegion
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
E.
foundOver
Indicates that one entity has discovered or identified another entity located above or higher than a reference point or surface.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2d01f9c8190849f252f22519550 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.