Triple
T32115977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster.com Park |
E820238
|
entity |
| Predicate | correctSponsoredName |
P15097
|
FINISHED |
| Object | Monster Park |
—
|
NE NERFINISHED |
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: Monster Park | Statement: [Monster.com Park, correctSponsoredName, Monster Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correctSponsoredName Context triple: [Monster.com Park, correctSponsoredName, Monster Park]
-
A.
sponsorFrom
Indicates that one entity provides sponsorship or financial backing originating from a specified source entity.
-
B.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
C.
sponsorshipNameAdopted
Indicates that an entity has adopted or taken on a specific sponsorship name as its official or recognized designation.
-
D.
sponsorshipName
chosen
Indicates the name or title associated with a sponsorship relationship between entities.
-
E.
sponsorTo
Indicates that one entity provides support, funding, or endorsement to another entity, typically to enable or promote the latter’s activities or initiatives.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 12:28 a.m.