Triple
T37463102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherazin, Corpse Flower |
E930966
|
entity |
| Predicate | zoneBehavior |
P187947
|
FINISHED |
| Object | returns to battlefield from dormant state on board |
—
|
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: returns to battlefield from dormant state on board | Statement: [Sherazin, Corpse Flower, zoneBehavior, returns to battlefield from dormant state on board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneBehavior Context triple: [Sherazin, Corpse Flower, zoneBehavior, returns to battlefield from dormant state on board]
-
A.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
B.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
-
C.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
D.
regionBehavior
Indicates how an entity acts, functions, or changes within a specific region or spatial area.
-
E.
zoneStatus
Indicates the current operational or condition state assigned to a specific zone within a system or environment.
- 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.