Triple
T8266019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitanni |
E193302
|
entity |
| Predicate | vassalStates |
P47437
|
FINISHED |
| Object | Syrian city-states |
—
|
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: Syrian city-states | Statement: [Mitanni, vassalStates, Syrian city-states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vassalStates Context triple: [Mitanni, vassalStates, Syrian city-states]
-
A.
vassalState
chosen
Indicates a relationship where one political entity is subordinate to and under the authority or control of another, typically more powerful, state.
-
B.
sovereignState
Indicates that an entity is recognized as an independent, self-governing state with ultimate authority over its territory and not subject to any higher political power.
-
C.
vassalsOf
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of another entity.
-
D.
realmRuled
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
-
E.
multiNationalState
Indicates a state whose population is composed of multiple distinct national or ethnic groups under a single political authority.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794c54448190a685b8d0070980d7 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:50 p.m.