Triple
T4371224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Something’s Burning |
E98899
|
entity |
| Predicate | hasProductionFeature |
P54468
|
FINISHED |
| Object | lush arrangement |
—
|
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: lush arrangement | Statement: [Something’s Burning, hasProductionFeature, lush arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductionFeature Context triple: [Something’s Burning, hasProductionFeature, lush arrangement]
-
A.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
B.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
C.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
hasProductionAspect
chosen
Indicates that something possesses or involves a particular aspect, feature, or characteristic related to its production process or creation.
-
E.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521dffbc8190b9300a7f4f64bdc0 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.