Triple
T508215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Ellum |
E10547
|
entity |
| Predicate | hasEventType |
P14526
|
FINISHED |
| Object | live concerts |
—
|
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: live concerts | Statement: [Deep Ellum, hasEventType, live concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventType Context triple: [Deep Ellum, hasEventType, live concerts]
-
A.
hasSubEvent
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
B.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
-
C.
hasCampType
Indicates that an entity is associated with or classified by a particular type or category of camp.
-
D.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
E.
hasNodeType
Indicates that an entity is associated with, or classified as, a specific type of node within a structured system or model.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f14dcd688190ad47a3b31b95b6d4 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfe236481909901cc7d4281b33c |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebbd70481908b462296671de67b |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.