Triple
T11250789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MonstroCity: Rampage |
E266315
|
entity |
| Predicate | hasResourceManagement |
P86412
|
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, hasResourceManagement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResourceManagement Context triple: [MonstroCity: Rampage, hasResourceManagement, true]
-
A.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
B.
managesResourceType
chosen
Indicates that an entity is responsible for overseeing, controlling, or administering a particular type or category of resource.
-
C.
hasResourceBase
Indicates that one entity possesses, is founded on, or derives from another entity serving as its fundamental resource or base.
-
D.
hasMajorResource
Indicates that an entity possesses or is characterized by a primary or most significant resource.
-
E.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
- 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_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. |
Created at: April 8, 2026, 9:31 p.m.