Triple
T3193532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antium |
E66880
|
entity |
| Predicate | functionInEmpire |
P30862
|
FINISHED |
| Object | elite retreat |
—
|
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: elite retreat | Statement: [Antium, functionInEmpire, elite retreat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInEmpire Context triple: [Antium, functionInEmpire, elite retreat]
-
A.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
B.
associatedEmpire
Indicates a relationship where one entity is linked or connected to a particular empire, typically as belonging to, originating from, or being under the influence or control of that empire.
-
C.
cosmicFunction
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
-
D.
functionInPapalCourt
Indicates that an entity holds or performs an official role, duty, or service within the administrative or ceremonial structure of the papal court.
-
E.
functionInSystem
chosen
Indicates that an entity serves a specific role or performs a particular function within a given system.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada713bf0c81908f3143f45f63a5ad |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.