Triple
T8786155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Your Eyes |
E209046
|
entity |
| Predicate | hasIconicCulturalStatus |
P1579
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [In Your Eyes, hasIconicCulturalStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconicCulturalStatus Context triple: [In Your Eyes, hasIconicCulturalStatus, true]
-
A.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
B.
hasCulturalSignificance
chosen
Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
-
C.
hasCulturalProtection
Indicates that an entity is subject to legal or formal measures intended to preserve and safeguard its cultural value or heritage.
-
D.
culturalHeritageRecognizedBy
Indicates that an entity’s cultural heritage status has been formally acknowledged or designated by a specific recognizing authority or organization.
-
E.
isCulturalSignificance
Indicates that something holds notable meaning, value, or influence 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f758d348190804942d985f2337c |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.