Triple
T37953865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midnight Robber |
E946810
|
entity |
| Predicate | hasPerformanceFeature |
P72988
|
FINISHED |
| Object | boastful speeches |
—
|
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: boastful speeches | Statement: [Midnight Robber, hasPerformanceFeature, boastful speeches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceFeature Context triple: [Midnight Robber, hasPerformanceFeature, boastful speeches]
-
A.
hasVehicleFeature
Indicates that a vehicle possesses, includes, or is equipped with a specific feature or characteristic.
-
B.
hasSideFeature
Indicates that an entity possesses a specific secondary or auxiliary feature on its side or lateral aspect.
-
C.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
D.
performanceFeature
chosen
Indicates that an entity possesses a characteristic, capability, or attribute specifically related to its performance or operational effectiveness.
-
E.
hasPerformanceProfile
Indicates that an entity is associated with a specific performance profile that characterizes its performance attributes or behavior.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:20 p.m.