Triple
T6166821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ground Zero |
E137583
|
entity |
| Predicate | hasLevelType |
P69163
|
FINISHED |
| Object | scenario-based level |
—
|
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: scenario-based level | Statement: [Ground Zero, hasLevelType, scenario-based level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelType Context triple: [Ground Zero, hasLevelType, scenario-based level]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
hasCategoryLevel
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
-
C.
hasNumberOfLevels
Indicates that an entity possesses a specified count of distinct levels or tiers.
-
D.
hasLocalLevel
Indicates that one entity possesses, is associated with, or is defined at a specific local administrative or organizational level relative to another entity.
-
E.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d6366948190b35ef44dd9d6fcd6 |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:17 p.m.