Triple
T19015320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strawberry City |
E465332
|
entity |
| Predicate | isLocalNickname |
P11214
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Strawberry City, isLocalNickname, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalNickname Context triple: [Strawberry City, isLocalNickname, yes]
-
A.
isNickname
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
-
B.
localNickname
chosen
Indicates that an entity is known by a particular nickname within a specific local or regional context.
-
C.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
D.
isLocalTo
Indicates that one entity is geographically or contextually situated near, or within the same local area or scope as, another entity.
-
E.
hasNicknameStatus
Indicates that an entity holds a particular status or classification specifically related to its nickname.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6d9f2a081908c0e923809da88e2 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.