Triple
T26681990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankee |
E672635
|
entity |
| Predicate | canBePerceivedAs |
P76859
|
FINISHED |
| Object | offensive in some contexts |
—
|
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: offensive in some contexts | Statement: [Yankee, canBePerceivedAs, offensive in some contexts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePerceivedAs Context triple: [Yankee, canBePerceivedAs, offensive in some contexts]
-
A.
canBeViewedAs
chosen
Indicates that one entity may be interpreted, treated, or understood as another entity or type under some perspective or conditions.
-
B.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
C.
perceptionByHumans
Indicates that something is perceived, sensed, or experienced through human sensory or cognitive processes.
-
D.
canBeUnderstoodBy
Indicates that something is comprehensible or interpretable to a particular entity or group.
-
E.
canBeDepictedAs
Indicates that one entity is capable of being visually represented or illustrated in the form or style of another entity.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 3:20 a.m.