Triple
T19601118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sicel culture |
E470476
|
entity |
| Predicate | gradualAssimilationInto |
P9863
|
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: [Sicel culture, gradualAssimilationInto, Greek culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradualAssimilationInto Context triple: [Sicel culture, gradualAssimilationInto, Greek culture]
-
A.
adoptedGraduallyBy
chosen
Indicates that one entity is taken up, accepted, or implemented by another entity in a slow, incremental, or phased manner over time.
-
B.
languageOfAssimilation
Indicates the language used to integrate or absorb individuals or groups into a dominant culture or society.
-
C.
culturalAssimilationInto
Indicates a process where one entity adopts or integrates into the cultural norms, values, and practices of another entity or group.
-
D.
partiallyIncorporatedInto
Indicates that one entity has been integrated or absorbed into another entity, but only to a limited or incomplete extent.
-
E.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407f1fd88190aa82c4c96f755584 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.