Triple
T1761718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assyria |
E38671
|
entity |
| Predicate | rulingClass |
P9679
|
FINISHED |
| Object | kings |
—
|
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: kings | Statement: [Assyria, rulingClass, kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingClass Context triple: [Assyria, rulingClass, kings]
-
A.
rulingHouse
Indicates that one entity serves as the dynastic or noble family that holds ruling authority over another entity, such as a state, territory, or polity.
-
B.
nobilityClass
chosen
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
C.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
D.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
-
E.
aristocraticRole
Indicates that an entity holds or is associated with a formal position, title, or function within an aristocratic or noble 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.