Triple
T6304711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaka Regency |
E141344
|
entity |
| Predicate | hasLocalDeputyExecutive |
P40999
|
FINISHED |
| Object | vice regent |
—
|
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: vice regent | Statement: [Malaka Regency, hasLocalDeputyExecutive, vice regent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalDeputyExecutive Context triple: [Malaka Regency, hasLocalDeputyExecutive, vice regent]
-
A.
deputyOf
Indicates that one entity serves as the subordinate or second-in-command to another, acting with delegated authority on their behalf.
-
B.
mayHaveDeputy
Indicates that an entity is allowed or entitled to have another entity serving as its deputy or subordinate representative.
-
C.
hasDeputeLeader
chosen
Indicates that an entity serves as the deputy leader (second-in-command) of another entity.
-
D.
hasDeputyLeaderTitle
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
E.
deputyMinister
Indicates that one entity serves as the deputy minister (second-in-command or subordinate minister) to another entity within a governmental or ministerial hierarchy.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645f26a881909d5746151c0843cc |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.