Triple
T35806237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Brahma Bull |
E1035106
|
entity |
| Predicate | hasFanRecognitionAs |
P27251
|
FINISHED |
| Object | iconic nickname of The Rock |
—
|
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: iconic nickname of The Rock | Statement: [The Brahma Bull, hasFanRecognitionAs, iconic nickname of The Rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanRecognitionAs Context triple: [The Brahma Bull, hasFanRecognitionAs, iconic nickname of The Rock]
-
A.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
-
B.
hasFanPerception
chosen
Indicates that an entity is perceived, interpreted, or regarded in a particular way by its fans or fan community.
-
C.
wasRecognizedAs
Indicates that an entity was formally identified, acknowledged, or designated as having a particular role, status, or quality.
-
D.
hasFanTributeUse
Indicates that something is used, referenced, or incorporated within a fan-created tribute to a work, person, or entity.
-
E.
hasReceivedRecognitionFor
Indicates that an entity has been acknowledged, honored, or formally recognized for a particular achievement, contribution, or quality.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:06 p.m.