Triple
T28660629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxima Caesariensis |
E725457
|
entity |
| Predicate | likelyCapital |
P66247
|
FINISHED |
| Object | Londinium |
—
|
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: Londinium | Statement: [Maxima Caesariensis, likelyCapital, Londinium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyCapital Context triple: [Maxima Caesariensis, likelyCapital, Londinium]
-
A.
possibleCapital
chosen
Indicates that a location is a candidate or potential capital city of a given political or administrative entity.
-
B.
madeCapital
Indicates that one entity was designated or established as the capital city of another entity (such as a country, state, or region).
-
C.
connectsCapital
Indicates a relationship where one entity serves as the capital city that is officially linked to or associated with another entity, such as a country or region.
-
D.
coversCapital
Indicates that one entity provides coverage, service, or applicability specifically to the capital city of another entity.
-
E.
alternativeCapital
Indicates that one location serves as an alternative or secondary capital city in relation to another primary capital.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 4:57 a.m.