Triple
T30712974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleja |
E781940
|
entity |
| Predicate | hasNicknameFunction |
P170055
|
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: [Aleja, hasNicknameFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNicknameFunction Context triple: [Aleja, hasNicknameFunction, yes]
-
A.
hasNicknameStatus
Indicates that an entity holds a particular status or classification specifically related to its nickname.
-
B.
hasNicknameForm
Indicates that one entity is a nickname or informal variant form of another entity’s name.
-
C.
hasNicknamedFeature
Indicates that an entity possesses a feature or attribute that is commonly referred to by a specific nickname.
-
D.
isNickname
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
-
E.
usesNicknameIn
Indicates that one entity refers to another entity by a specific nickname within a particular context or setting.
- F. None of above. chosen
Provenance (4 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c1fd1e081908fa0a55e82f3030b |
completed | May 2, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:35 p.m.