Triple
T10056516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Spain |
E208874
|
entity |
| Predicate | culturalProcess |
P7515
|
FINISHED |
| Object | Romanization |
—
|
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: Romanization | Statement: [Roman Spain, culturalProcess, Romanization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalProcess Context triple: [Roman Spain, culturalProcess, Romanization]
-
A.
culturalMovement
chosen
Indicates that an entity is associated with, participates in, or belongs to a particular cultural movement or trend.
-
B.
culturalPreservation
Indicates efforts or actions aimed at maintaining, protecting, and transmitting cultural traditions, practices, and heritage over time.
-
C.
culturalLayer
Indicates the relationship in which something belongs to, originates from, or is associated with a particular cultural stratum, tradition, or level within a culture.
-
D.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
E.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfae503881909b9f016da4e2207d |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.