Triple
T32877143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcan fight theme |
E840957
|
entity |
| Predicate | hasNotableSceneElement |
P3574
|
FINISHED |
| Object | use of bladed lirpa weapons |
—
|
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: use of bladed lirpa weapons | Statement: [Vulcan fight theme, hasNotableSceneElement, use of bladed lirpa weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSceneElement Context triple: [Vulcan fight theme, hasNotableSceneElement, use of bladed lirpa weapons]
-
A.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
B.
containsScene
Indicates that one entity (typically a media item or narrative work) includes or features a particular scene as part of its content.
-
C.
hasNotableSegment
chosen
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
-
D.
hasNotableStructureOn
Indicates that a subject entity possesses or features a significant or noteworthy structure located on it.
-
E.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
Created at: May 1, 2026, 1:18 a.m.