Triple
T37458976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antique Healbot |
E930869
|
entity |
| Predicate | canAppearInArena |
P187899
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Antique Healbot, canAppearInArena, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAppearInArena Context triple: [Antique Healbot, canAppearInArena, true]
-
A.
playedInArena
Indicates that an entity (typically a performer or team) participated in an event that took place within a specific arena.
-
B.
hasPrimaryArena
Indicates that an entity is associated with its main or principal arena where it primarily hosts or performs its activities.
-
C.
madeArenaCupAppearance
Indicates that an entity has participated in at least one appearance in an Arena Cup competition or event.
-
D.
hasPvPArea
Indicates that a location or zone is designated for player-versus-player (PvP) interactions or combat.
-
E.
associatedWithArena
Indicates a relationship in which an entity is linked or connected to a particular arena, such as by location, use, affiliation, or operation.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.