Triple
T24976423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Chopper |
E625034
|
entity |
| Predicate | hasFrameStyle |
P76579
|
FINISHED |
| Object | chopper-style frame |
—
|
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: chopper-style frame | Statement: [Raleigh Chopper, hasFrameStyle, chopper-style frame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrameStyle Context triple: [Raleigh Chopper, hasFrameStyle, chopper-style frame]
-
A.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
hasFrameElement
Indicates that a frame (or structured conceptual scenario) includes or is associated with a specific frame element (a participant, role, or component within that frame).
-
C.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
D.
hasFrameType
chosen
Indicates that an entity possesses or is associated with a specific type or category of frame.
-
E.
hasPowerStyle
Indicates that one entity possesses or exhibits a particular style or manner of using power in relation to another entity or context.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:02 a.m.