Triple
T28359276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verlamion |
E718317
|
entity |
| Predicate | countryInIronAge |
P196494
|
FINISHED |
| Object | Britain |
—
|
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: Britain | Statement: [Verlamion, countryInIronAge, Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryInIronAge Context triple: [Verlamion, countryInIronAge, Britain]
-
A.
countryDuringAntiquity
Indicates that an entity functioned as a country or political territory specifically during the historical period of antiquity.
-
B.
ancientStates
Indicates that the related entity functioned as a state or political entity in ancient times.
-
C.
countryOfFortress
Indicates that a fortress is located within and belongs to the territory of a specific country.
-
D.
countryDuringCrusades
Indicates that an entity functioned as or corresponded to a particular country during the historical period of the Crusades.
-
E.
countryDuringByzantinePeriod
Indicates that a modern or historical country existed within, or is contextually associated with, the geographic or political realm of the Byzantine Empire during the Byzantine period.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: April 28, 2026, 12:51 a.m.