Triple
T33049046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priscus of Panium |
E845674
|
entity |
| Predicate | embassyDestination |
P169865
|
FINISHED |
| Object | court of Attila the Hun |
—
|
NE NERFINISHED |
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: court of Attila the Hun | Statement: [Priscus of Panium, embassyDestination, court of Attila the Hun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embassyDestination Context triple: [Priscus of Panium, embassyDestination, court of Attila the Hun]
-
A.
mainEmbassyName
Indicates the official or primary name assigned to a country’s main embassy in a given location.
-
B.
diplomaticMissionInCity
Indicates that a diplomatic mission (such as an embassy or consulate) is located in or operates within a specific city.
-
C.
ledLegationTo
chosen
Indicates that one entity headed or directed a diplomatic mission or delegation to another entity or location.
-
D.
relationshipToEmbassy
Indicates the type of formal or personal connection an entity has with a specific embassy.
-
E.
hasDiplomaticStaffFrom
Indicates that an entity has diplomatic personnel who originate from or represent another specified entity.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:24 a.m.