Triple
T37883427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Big Ears |
E944932
|
entity |
| Predicate | mayBePerceivedAs |
P76859
|
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: [Old Big Ears, mayBePerceivedAs, affectionate nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBePerceivedAs Context triple: [Old Big Ears, mayBePerceivedAs, affectionate nickname]
-
A.
canBeViewedAs
chosen
Indicates that one entity may be interpreted, treated, or understood as another entity or type under some perspective or conditions.
-
B.
mayAppear
Indicates that an entity is allowed or has the possibility to be present or occur in association with another entity or context.
-
C.
intendedPerception
Indicates that one entity is meant or designed to be perceived (e.g., seen, heard, or otherwise sensed) by another entity.
-
D.
culturallyPerceivedAs
Indicates that one entity is regarded or interpreted in a particular way by a culture or cultural group.
-
E.
perceivedAttribute
Indicates that one entity recognizes, interprets, or assigns a particular attribute or quality to 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:19 p.m.