Triple
T11250793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MonstroCity: Rampage |
E266315
|
entity |
| Predicate | hasGuildsOrAlliances |
P98704
|
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: [MonstroCity: Rampage, hasGuildsOrAlliances, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuildsOrAlliances Context triple: [MonstroCity: Rampage, hasGuildsOrAlliances, true]
-
A.
hasAllianceInState
Indicates that an alliance or cooperative relationship exists between entities within a specified state or jurisdiction.
-
B.
hasMemberOrganizationsIn
Indicates that an entity includes or comprises member organizations that are located in or associated with a specified place or region.
-
C.
hasMultiClubNetwork
Indicates that an entity is part of, or associated with, a network comprising multiple clubs under common ownership, management, or affiliation.
-
D.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
E.
hasAllianceFocus
Indicates that an entity is oriented toward, prioritizes, or concentrates its efforts on maintaining or developing an alliance relationship with another entity.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e93212448190b46b3799b0bdfa0f |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.