Triple
T21500330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pech language |
E530456
|
entity |
| Predicate | closelyAssociatedCulture |
P1439
|
FINISHED |
| Object | Pech 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: Pech culture | Statement: [Pech language, closelyAssociatedCulture, Pech culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closelyAssociatedCulture Context triple: [Pech language, closelyAssociatedCulture, Pech culture]
-
A.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
B.
associatedCult
Indicates that an entity is connected or linked to a particular cult, typically through membership, affiliation, or influence.
-
C.
hasCulturalRelation
Indicates a relationship in which entities are connected through shared, influencing, or interacting cultural practices, values, traditions, or expressions.
-
D.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
E.
countryOfCulturalSignificance
Indicates that a country holds notable cultural importance or influence for a given entity, such as a person, group, object, or practice.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea5ae154819090299773b373b921 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:24 p.m.