Triple
T34390606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Tarentum |
E882690
|
entity |
| Predicate | earlierCulturalSphere |
P187411
|
FINISHED |
| Object | Greek culture |
—
|
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: Greek culture | Statement: [Roman Tarentum, earlierCulturalSphere, Greek culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierCulturalSphere Context triple: [Roman Tarentum, earlierCulturalSphere, Greek culture]
-
A.
earlierFortificationCulture
Indicates that one culture’s fortification activity or tradition chronologically precedes that of another culture.
-
B.
regionOfEarlyCultivation
Indicates the geographic area where a particular species, crop, or practice was first or among the earliest to be cultivated.
-
C.
regionOfCulturalImpact
Indicates the geographic area where an entity’s cultural influence, activities, or effects are most significantly felt or observed.
-
D.
hasNearbyAncientCulture
Indicates that one entity is geographically close to another entity associated with an ancient culture or civilization.
-
E.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 1, 2026, 1:59 a.m.