Triple
T14451365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemu |
E358343
|
entity |
| Predicate | roleUnderSurEmpire |
P63168
|
FINISHED |
| Object | general |
—
|
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: general | Statement: [Hemu, roleUnderSurEmpire, general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleUnderSurEmpire Context triple: [Hemu, roleUnderSurEmpire, general]
-
A.
positionOnEmpire
chosen
Indicates that one entity holds a specific role, rank, or status within the hierarchical structure of an empire in relation to another entity.
-
B.
associatedEmpire
Indicates a relationship where one entity is linked or connected to a particular empire, typically as belonging to, originating from, or being under the influence or control of that empire.
-
C.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
-
D.
legalStatusInEmpire
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
-
E.
realmRuled
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916244948190bb09d1bfc485ba50 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.