Triple
T9662514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammon |
E233621
|
entity |
| Predicate | hadRulingClass |
P89474
|
FINISHED |
| Object | kings of Ammon |
—
|
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 of Ammon | Statement: [Ammon, hadRulingClass, kings of Ammon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRulingClass Context triple: [Ammon, hadRulingClass, kings of Ammon]
-
A.
rulingClassBackground
Indicates that an entity comes from, or is associated with, a socially or politically dominant (ruling) class background.
-
B.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
C.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
D.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
E.
heldUnderCivilRuler
Indicates that an event, position, or status occurred while a particular civil ruler was in power or authority.
- F. None of above. chosen
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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:14 p.m.