Triple
T1275882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsi |
E27211
|
entity |
| Predicate | associatedWithRomanceCulture |
P1439
|
FINISHED |
| Object | Corsican 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: Corsican culture | Statement: [Corsi, associatedWithRomanceCulture, Corsican culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRomanceCulture Context triple: [Corsi, associatedWithRomanceCulture, Corsican culture]
-
A.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
B.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
C.
associatedCult
Indicates that an entity is connected or linked to a particular cult, typically through membership, affiliation, or influence.
-
D.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
E.
usedInCulture
Indicates that something (such as an object, practice, or concept) is employed, referenced, or plays a role within a particular culture or cultural context.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.