Triple
T25134642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macon Knights |
E629622
|
entity |
| Predicate | madeArenaCupAppearance |
P157960
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Macon Knights, madeArenaCupAppearance, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeArenaCupAppearance Context triple: [Macon Knights, madeArenaCupAppearance, no]
-
A.
playedInArena
Indicates that an entity (typically a performer or team) participated in an event that took place within a specific arena.
-
B.
homeArenaChampion
Indicates that an entity is recognized as the champion or primary representative associated with a particular home arena.
-
C.
hostedInArenaUsedFor
Indicates that an event or activity is hosted in an arena that is (or was) used for a particular purpose or by a particular organization.
-
D.
playsInArenaLocatedIn
Indicates that an entity performs or participates in events within an arena that is geographically located in a specified place.
-
E.
hasPrimaryArena
Indicates that an entity is associated with its main or principal arena where it primarily hosts or performs its activities.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465febf508190a350d9e1f9b4dda5 |
completed | May 1, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:29 a.m.