Triple
T4553440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trife |
E120422
|
entity |
| Predicate | locatedInCulturalSphere |
P14191
|
FINISHED |
| Object | New York hip hop |
—
|
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: New York hip hop | Statement: [Trife, locatedInCulturalSphere, New York hip hop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCulturalSphere Context triple: [Trife, locatedInCulturalSphere, New York hip hop]
-
A.
countryOfCulturalSignificance
Indicates that a country holds notable cultural importance or influence for a given entity, such as a person, group, object, or practice.
-
B.
culturalSphere
chosen
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
C.
culturalAreaIncludes
Indicates that a broader cultural area encompasses or contains a smaller cultural region or entity within its scope.
-
D.
regionOfCulturalImpact
Indicates the geographic area where an entity’s cultural influence, activities, or effects are most significantly felt or observed.
-
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.
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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd581160e08190b715a8ce5c3e6c9b |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.