Triple
T27952130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altern-8 |
E703454
|
entity |
| Predicate | stageAppearanceFeature |
P165726
|
FINISHED |
| Object | gas masks |
—
|
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: gas masks | Statement: [Altern-8, stageAppearanceFeature, gas masks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageAppearanceFeature Context triple: [Altern-8, stageAppearanceFeature, gas masks]
-
A.
hasStageAppearance
Indicates that an entity makes or has made a performance or appearance on a stage, typically before an audience.
-
B.
hasStageAppearanceWith
Indicates that two or more entities appear together in the same staged performance or event.
-
C.
stageImage
Indicates that an image is being prepared, arranged, or set up for display or presentation in a particular context or environment.
-
D.
stageElement
Indicates that one entity functions as a component or part within the structure or configuration of another entity.
-
E.
stageTechnology
Indicates that a particular technology is used, implemented, or deployed at a specific stage or phase within a process, workflow, or lifecycle.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 27, 2026, 7:25 p.m.