Triple
T22894521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attila’s Throne |
E568133
|
entity |
| Predicate | likelyUse |
P150157
|
FINISHED |
| Object | seat of a local magistrate |
—
|
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: seat of a local magistrate | Statement: [Attila’s Throne, likelyUse, seat of a local magistrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyUse Context triple: [Attila’s Throne, likelyUse, seat of a local magistrate]
-
A.
likelyBehavior
Indicates the behavior or action that an entity is expected or predicted to exhibit under given circumstances.
-
B.
likelySource
Indicates that one entity is considered the probable origin or cause of another entity or event.
-
C.
likelyFuture
Indicates that one entity is predicted or expected to occur, hold, or be true at a future time relative to another reference point or context.
-
D.
likelyComposition
Indicates that one entity is probably a component or constituent part of another entity, though this compositional relationship is uncertain or inferred rather than definite.
-
E.
likelySocialBehavior
Indicates that an entity is expected or predicted to engage in a particular social behavior or interaction.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f17fc83d688190a8ab5ea0aad1e7ec |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:40 p.m.