Triple
T10251296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigantium |
E240346
|
entity |
| Predicate | previousCulture |
P60430
|
FINISHED |
| Object | Celtic |
—
|
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: Celtic | Statement: [Brigantium, previousCulture, Celtic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCulture Context triple: [Brigantium, previousCulture, Celtic]
-
A.
predecessorCulture
chosen
Indicates that one culture historically preceded and contributed to the development of another culture.
-
B.
successorCulture
Indicates that one culture directly follows and continues or replaces another culture in time, inheriting or building upon its traditions or characteristics.
-
C.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
D.
cultureLegacy
Indicates that one entity preserves, inherits, or is significantly shaped by the cultural traditions, values, or practices originating from another entity.
-
E.
primaryCulture
Indicates the main or dominant culture associated with an entity, typically in contrast to any secondary or additional cultures.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:29 a.m.