Triple
T13270246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longtucky |
E316036
|
entity |
| Predicate | sometimesPerceivedAs |
P108327
|
FINISHED |
| Object | affectionate nickname |
—
|
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: affectionate nickname | Statement: [Longtucky, sometimesPerceivedAs, affectionate nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesPerceivedAs Context triple: [Longtucky, sometimesPerceivedAs, affectionate nickname]
-
A.
intendedPerception
Indicates that one entity is meant or designed to be perceived (e.g., seen, heard, or otherwise sensed) by another entity.
-
B.
perceivedRole
chosen
Indicates the role or function that one entity is regarded or interpreted as having in relation to another, based on perception rather than objective status.
-
C.
influencedPerceptionOf
Indicates that one entity has affected, shaped, or altered how another entity is perceived or understood.
-
D.
mayAppear
Indicates that an entity is allowed or has the possibility to be present or occur in association with another entity or context.
-
E.
isSometimesClassifiedAs
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.