Triple
T28774263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Mongus |
E726491
|
entity |
| Predicate | supportedImperialPolicyOf |
P1086
|
FINISHED |
| Object | Emperor Zeno |
E36812
|
NE 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: Emperor Zeno | Statement: [Peter Mongus, supportedImperialPolicyOf, Emperor Zeno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedImperialPolicyOf Context triple: [Peter Mongus, supportedImperialPolicyOf, Emperor Zeno]
-
A.
supportsPolicy
chosen
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
B.
supportRules
Indicates that one entity provides justification, backing, or validation for the rules or constraints defined by another entity.
-
C.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
D.
supportedUnit
Indicates that one entity provides assistance, resources, or backing to another entity functioning as a unit or sub-organization.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
- F. None of above.
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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a02008fcf1c8190b5b6c285944c52e9 |
completed | May 11, 2026, 4:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25d8f25bc881909cc0762ae16d3264 |
completed | June 7, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_6a01ffd3ba008190b6f026bd4e6b9a37 |
completed | May 11, 2026, 4:12 p.m. |
Created at: April 28, 2026, 6:17 a.m.