Triple
T35762939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pula |
E1033925
|
entity |
| Predicate | hasNearbyHistoricalPeriod |
P51816
|
FINISHED |
| Object | Roman era |
—
|
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: Roman era | Statement: [Pula, hasNearbyHistoricalPeriod, Roman era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricalPeriod Context triple: [Pula, hasNearbyHistoricalPeriod, Roman era]
-
A.
hasNearbyHistoricPeriod
chosen
Indicates that one historic period occurs close in time or space to another historic period.
-
B.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
C.
hasHistoricVicinity
Indicates that one entity is located near or within an area of historical significance associated with another entity.
-
D.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
E.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
Created at: May 3, 2026, 4:06 p.m.